Search crate docs for specific features, error messages, or usage examples. Helps debug compilation issues or learn new APIs.
AI agents call search_doc to retrieve information from Cargo Doc MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and searches existing Rust documentation without creating, modifying, executing, or deleting any data. It is a read-only operation that retrieves information to aid developers in learning and debugging. The low severity reflects that misuse would at worst return irrelevant search results with no harmful consequences.
From the tool's definition The tool "search_doc" is described as enabling users to "search crate docs for specific features, error messages, or usage examples" and "helps debug compilation issues or learn new APIs." These are purely informational retrieval operations with no…
Documented attack patterns abuse exactly the kind of access search_doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cargo Doc MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_doc:
{
"version": "1",
"default": "deny",
"tools": {
"search_doc": {}
}
}search_doc 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 crate docs for specific features, error messages, or usage examples. Helps debug compilation issues or learn new APIs. It is categorised as a Read tool in the Cargo Doc MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cargo Doc MCP Server MCP server in PolicyLayer and add a rule for search_doc: 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 Cargo Doc MCP Server. Nothing to install.
search_doc 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_doc 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_doc. 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_doc is provided by the Cargo Doc MCP Server MCP server (spacemeowx2/cargo-doc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cargo Doc MCP Server, 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.
3 Cargo Doc MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.