Search for files in Google Drive
AI agents call gdrive_search to retrieve information from Google Drive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries file metadata from Google Drive without modifying, deleting, or executing any operations. It is a search/query operation with no side effects, fitting the Read category. Severity is low because search operations expose only file names and metadata that an authenticated user would typically access anyway.
From the tool's definition Tool name is 'gdrive_search' and description states 'Search for files in Google Drive'. The server description confirms this server allows 'listing, reading, and searching files' as read operations.
Attacks that exploit this kind of access
Search for files in Google Drive. It is categorised as a Read tool in the Google Drive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for gdrive_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 Drive MCP Server. Nothing to install.
gdrive_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 gdrive_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 gdrive_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.
gdrive_search is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/drive-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 →