AI agents call get_crate_documentation to retrieve information from Rust 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 Rust crate documentation from docs.rs, which is a read-only operation with no side effects. While the description is empty, the name and server context clearly indicate it fetches documentation. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only retrieve documentation that is already publicly available.
From the tool's definition Tool name is 'get_crate_documentation' and server provides 'access to Rust documentation from docs.rs, enabling search for crates, documentation, type information, feature flags, version information'.
Documented attack patterns abuse exactly the kind of access get_crate_documentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rust Docs MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_crate_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_crate_documentation": {}
}
}get_crate_documentation 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.
get_crate_documentation. It is categorised as a Read tool in the Rust Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rust Docs MCP Server MCP server in PolicyLayer and add a rule for get_crate_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 Rust Docs MCP Server. Nothing to install.
get_crate_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 get_crate_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 get_crate_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.
get_crate_documentation is provided by the Rust Docs MCP Server MCP server (laptou/rust-docs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rust Docs 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.
7 Rust Docs MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.