gdrive_search_files
Searches the synced Google Drive folder for files by name (recursive). Returns up to max_results matches (default 50).
This record as markdown: /tools/com-local-mcp-local-mcp/gdrive-search-files.md
What gdrive_search_files does on Local
AI agents call gdrive_search_files to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
root | string | — | Restrict to this Drive path (optional - defaults to all mounts) |
query | string | Yes | Filename pattern to search for |
max_results | integer | — | Maximum results (default 50) |
Parameters from the server's own tool schema.
Why gdrive_search_files is rated Low
This tool queries existing data (files in Google Drive) without creating, modifying, deleting, or executing any operations. It is a passive read operation that retrieves information based on search criteria. The worst-case misuse would be unauthorized discovery of file names, which is a low-severity information disclosure risk rather than a high-impact security event.
From the tool's definition Tool performs a search operation on synced Google Drive files by name and returns matches. The verb 'search' and the read-only nature of querying without modifying or executing operations indicates this is a retrieval function.
Attacks that exploit this kind of access
The rule that runs gdrive_search_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gdrive_search_files, this is the rule to start with:
gdrive_search_files is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every gdrive_search_files call is checked against it from then on.
Questions about gdrive_search_files
Searches the synced Google Drive folder for files by name (recursive). Returns up to max_results matches (default 50). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
gdrive_search_files accepts 3 parameters: root, query, max_results. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for gdrive_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 Local. Nothing to install.
gdrive_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 gdrive_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 gdrive_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.
gdrive_search_files is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue