drive_changes_watch

Subscribe to changes for a user or shared drive

Part of the Google Workspace Drive (gws CLI) MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@gws mcp -s drive Read Risk 2/5

// WHEN AI AGENTS USE THIS TOOL

AI agents call drive_changes_watch to retrieve information from Google Workspace Drive (gws CLI) without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON DRIVE_CHANGES_WATCH

Even though drive_changes_watch only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

google-workspace-drive.yaml

tools:
  drive_changes_watch:
    rules:
      - action: allow

See the full Google Workspace Drive (gws CLI) policy for all 57 tools.

// DETAILS

Tool Name drive_changes_watch

Category Read

MCP Server Google Workspace Drive (gws CLI) MCP Server

Risk Level Low

// MORE GOOGLE WORKSPACE DRIVE (GWS CLI) TOOLS

Destructive drive_comments_delete Destructive drive_drives_delete Destructive drive_files_delete Destructive drive_files_emptyTrash Destructive drive_permissions_delete Destructive drive_replies_delete Destructive drive_revisions_delete Destructive drive_teamdrives_delete

View all 57 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like drive_changes_watch have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the drive_changes_watch tool do? +

Subscribe to changes for a user or shared drive. It is categorised as a Read tool in the Google Workspace Drive (gws CLI) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on drive_changes_watch? +

Add a rule in your Intercept YAML policy under the tools section for drive_changes_watch. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Workspace Drive (gws CLI) MCP server.

What risk level is drive_changes_watch? +

drive_changes_watch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit drive_changes_watch? +

Yes. Add a rate_limit block to the drive_changes_watch rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block drive_changes_watch completely? +

Set action: deny in the Intercept policy for drive_changes_watch. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides drive_changes_watch? +

drive_changes_watch is provided by the Google Workspace Drive (gws CLI) MCP server (@gws mcp -s drive). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

drive_changes_watch

Enforce policies on Google Workspace Drive (gws CLI)