Search Drive files visible to Hermes by filename.
AI agents call drive_search to retrieve information from Hermes Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
drive_search performs a search query over existing Drive files, returning results based on a filename criterion. It has no side effects, does not modify data, does not execute code, and does not delete or move files. It is a straightforward read operation. The confidence is high because the description is clear and unambiguous about its search-only nature.
From the tool's definition The tool description states it 'Search[es] Drive files visible to Hermes by filename.' This is a query operation that retrieves or lists data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Search Drive files visible to Hermes by filename. It is categorised as a Read tool in the Hermes Google MCP Server, which means it retrieves data without modifying state.
Register the Hermes Google 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 Hermes Google. 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 Hermes Google MCP server (jimmy-larsson/hermes-google). 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 →