[BUG] Google Drive connector requests drive.readonly scope in addition to drive.file, granting full-Drive read access despite "specific files only" consent UI

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When connecting the Google Drive connector (in claude.ai, Claude Desktop, or Cowork), the OAuth consent screen presents the scope as limited — "See, edit, create, and delete only the specific Google Drive files you use with this app" (drive.file). However, inspecting the token issued after authorization shows that drive.readonly is granted alongside drive.file in the same OAuth client.

drive.file is scoped to files the user explicitly selects via the picker or that the app creates. drive.readonly grants read access to the user's entire Drive corpus ("See and download all of your Google Drive files"), per Google's own scope documentation.

This can be independently verified by any user at myaccount.google.com/permissions after connecting: the permissions listing shows access to all files in Drive, not just files selected through the connector's picker UI.

Because both scopes are requested by a single OAuth client at connect time, there is no way for a user to grant only drive.file — it's all-or-nothing. The consent screen's wording ("only the specific files you use with this app") does not reflect the actual scope being requested.

So to summarize the actual behavior:
The OAuth token includes drive.readonly in addition to drive.file, giving Claude read access to the user's entire Drive — including files never selected via the connector — with no user-facing option to decline the broader scope.

What Should Happen?

The OAuth request should only include drive.file, matching the consent screen's stated scope ("only the specific files you use with this app"). Users who want to grant Claude access only to files/folders they explicitly select should be able to do so, without also granting read access to their entire Drive.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

1. Go to Settings > Connectors > Google Drive > Connect
2. Complete the Google OAuth consent flow
3. Go to https://myaccount.google.com/permissions
4. Find the Claude/Anthropic Drive connector entry and inspect granted scopes

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.30096.1 (194d93) 2026-08-13T21:28:02.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

WHY THIS MATTERS
This is a least-privilege violation: the consent UI implies narrow, file-specific access, but the actual granted scope is far broader. Users making access decisions based on the displayed consent language are unknowingly granting full-Drive read visibility. This is particularly concerning for accounts with sensitive files shared by others, old files the user has forgotten about, or enterprise/Workspace accounts subject to data-handling policies — since the discrepancy between stated and actual scope isn't discoverable without manually checking Google's third-party access page.