Search for Google Docs by title or content
AI agents call google_docs_search to retrieve information from Google Docs MCP Server 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 against Google Docs, returning matching documents based on title or content. It retrieves information without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could search for sensitive documents, but cannot alter or destroy them. This is a straightforward Read operation.
From the tool's definition Tool name 'google_docs_search' and description 'Search for Google Docs by title or content' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Search for Google Docs by title or content. It is categorised as a Read tool in the Google Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for google_docs_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 Docs MCP Server. Nothing to install.
google_docs_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 google_docs_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 google_docs_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.
google_docs_search is provided by the Google Docs MCP Server MCP server (meerkats-ai/google-docs-mcp-server). 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 →