Search files and folders in Google Drive using query syntax
AI agents call search_drive_files to retrieve information from VaultAssist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about files and folders in Google Drive but does not create, modify, delete, or execute any actions. It is a read-only search operation, presenting minimal risk. The severity is low because search results themselves do not directly impact system state or security, though an agent could use search results to inform subsequent actions on other tools.
From the tool's definition Tool name 'search_drive_files' and description 'Search files and folders in Google Drive using query syntax' indicate a query/retrieval operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access search_drive_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for search_drive_files:
{
"version": "1",
"default": "deny",
"tools": {
"search_drive_files": {}
}
}search_drive_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 files and folders in Google Drive using query syntax. It is categorised as a Read tool in the VaultAssist MCP Server, which means it retrieves data without modifying state.
Register the VaultAssist MCP server in PolicyLayer and add a rule for search_drive_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 VaultAssist. Nothing to install.
search_drive_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 search_drive_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 search_drive_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.
search_drive_files is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, 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.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.