search_documentation
AI agents call search_documentation to retrieve information from Gemini 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 retrieves data from a documentation database without side effects. It performs a search/query operation on stored documentation, which is a Read category action. Severity is low because searching documentation poses minimal risk—the worst outcome is information disclosure about a public API, which is already documented. Confidence is slightly reduced (0.85 vs.
From the tool's definition Tool name 'search_documentation' and server context indicate querying/retrieving documentation. Server description explicitly states 'search and retrieve Google Gemini API documentation' and 'full-text search capabilities'.
Attacks that exploit this kind of access
search_documentation. It is categorised as a Read tool in the Gemini Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gemini Docs MCP Server MCP server in PolicyLayer and add a rule for search_documentation: 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 Gemini Docs MCP Server. Nothing to install.
search_documentation 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_documentation 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_documentation. 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_documentation is provided by the Gemini Docs MCP Server MCP server (philschmid/gemini-api-docs-mcp). 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 →