AI agents call search_docs to retrieve information from Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs keyword and semantic search operations across pre-indexed documentation. Search is a read-only operation that retrieves data without side effects, modifying state, executing code, or committing financial transactions. The severity is low because misuse would only expose documentation content that is typically intended to be publicly searchable.
From the tool's definition Tool description states 'Search across indexed documentation sites' with search algorithms (BM25, vector embedding, hybrid, automatic mode).
Attacks that exploit this kind of access
Search across indexed documentation sites with BM25, vector embedding, hybrid (RRF), or automatic mode. It is categorised as a Read tool in the Docs MCP Server, which means it retrieves data without modifying state.
Register the Docs MCP server in PolicyLayer and add a rule for search_docs: 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 Docs. Nothing to install.
search_docs 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_docs 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_docs. 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_docs is provided by the Docs MCP server (kage1020/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 →