searchInCrate
AI agents call searchInCrate to retrieve information from Mcp Docsrs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches within a Rust crate's documentation. It retrieves information without side effects. No data is created, modified, deleted, or executed. The lack of a description reduces confidence slightly, but context from sibling tools and the server's read-only documentation access purpose strongly indicates a Read classification.
From the tool's definition Tool name 'searchInCrate' and sibling tools indicate read-only documentation access. Siblings include 'getCrateInfo', 'getItemDefinition', 'getItemExamples', 'listFeatures', 'searchCrates' — all queries of Rust crate documentation with no modification…
Attacks that exploit this kind of access
searchInCrate. It is categorised as a Read tool in the Mcp Docsrs MCP Server, which means it retrieves data without modifying state.
Register the Mcp Docsrs MCP server in PolicyLayer and add a rule for searchInCrate: 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 Mcp Docsrs. Nothing to install.
searchInCrate 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 searchInCrate 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 searchInCrate. 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.
searchInCrate is provided by the Mcp Docsrs MCP server (shuakami/mcp-docsrs). 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 →