Search for traits, structs, methods, etc. from the crate
AI agents call docs_rs_search_in_crate to retrieve information from Docs Rs MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Rust crate contents from docs.rs documentation. It performs queries against existing documentation data with no side effects, no code execution, no data modification, and no deletion. The blast radius of misuse is minimal — an agent could only waste time searching or retrieve redundant documentation. This is clearly a Read category tool.
From the tool's definition Tool description: 'Search for traits, structs, methods, etc. from the crate' — search is a read-only operation that queries documentation without modifying data.
Documented attack patterns abuse exactly the kind of access docs_rs_search_in_crate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docs Rs MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for docs_rs_search_in_crate:
{
"version": "1",
"default": "deny",
"tools": {
"docs_rs_search_in_crate": {}
}
}docs_rs_search_in_crate 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 for traits, structs, methods, etc. from the crate. It is categorised as a Read tool in the Docs Rs MCP MCP Server, which means it retrieves data without modifying state.
Register the Docs Rs MCP server in PolicyLayer and add a rule for docs_rs_search_in_crate: 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 Rs MCP. Nothing to install.
docs_rs_search_in_crate 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 docs_rs_search_in_crate 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 docs_rs_search_in_crate. 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.
docs_rs_search_in_crate is provided by the Docs Rs MCP server (nuskey8/docs-rs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Docs Rs MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Docs Rs MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.