List/search files. query uses Drive query language; see
AI agents call drive_search to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches for files in Google Drive without modifying, deleting, or executing them. It is a read-only operation with no side effects. Severity is low because search results expose file metadata that an attacker could use for reconnaissance, but the blast radius is limited to information disclosure without the ability to access file contents (that would require drive_file_download) or make…
From the tool's definition Tool name is 'drive_search' and description states 'List/search files' with a `query` parameter using Drive query language. No modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
List/search files. query uses Drive query language; see. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace 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 Google Workspace. 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 Google Workspace MCP server (rajool/google-workspace-mcp). 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 →