Search for files in your Google Drive by name or content. Args: - query (string): Search query - searches file names and content - page_size (number): Max files to return, 1-100 (default: 20) - page_token (string, optional): Pagination token for next page - mime_type (
AI agents call drive_search_files 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 performs a search/query operation that retrieves file metadata from Google Drive without creating, modifying, or deleting any data. It has no side effects and returns results only. This is clearly a read-only operation with minimal risk if misused by an AI agent—worst case would be unauthorized information disclosure of file names the user has access to.
From the tool's definition Tool description states 'Search for files in your Google Drive by name or content' with parameters for query, pagination, and optional filtering. No modification, deletion, or execution capabilities are mentioned.
Documented attack patterns abuse exactly the kind of access drive_search_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for drive_search_files:
{
"version": "1",
"default": "deny",
"tools": {
"drive_search_files": {}
}
}drive_search_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for files in your Google Drive by name or content. Args: - query (string): Search query - searches file names and content - page_size (number): Max files to return, 1-100 (default: 20) - page_token (string, optional): Pagination token for next page - mime_type (. 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_files: 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_files 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_files 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_files. 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_files is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.