AI agents call drive_search to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves file metadata from Google Drive. However, elevated to medium severity (rather than low) because: (1) it operates within a credential store/API proxy that aggregates access to multiple services, (2) search results could reveal sensitive document inventory and organizational structure, (3) in a multi-agent environment with per-agent permissioning, a compromised agent could…
From the tool's definition Tool performs search operations on Google Drive returning metadata (file IDs, names, MIME types, modification dates) with no modification capability. Description explicitly states 'Search' and 'find' operations typical of Read category.
Attacks that exploit this kind of access
Search Google Drive files using the Drive API query syntax. Use this to find documents, spreadsheets, or any file by name, type, or content. Returns file IDs, names, MIME types, and modification dates. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for drive_search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Access. Nothing to install.
drive_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the drive_search rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for drive_search. 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.
drive_search is provided by the Access MCP server (scottpedia0/access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →