crates_search
Search Rust crates on crates.io by name or keyword.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/crates-search.md
What crates_search does on UnClick
AI agents call crates_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Crate name or keyword. |
per_page | number | — | Results per page (default 10, max 50). |
Parameters from the server's own tool schema.
Why crates_search is rated Low
This tool retrieves and queries publicly available metadata about Rust crates from crates.io. It performs no modifications, deletions, or side effects—purely information retrieval. The search operation is a read-only lookup against a public repository, making it the lowest-risk category.
From the tool's definition Tool name 'crates_search' and description 'Search Rust crates on crates.io by name or keyword' indicate a read-only query operation against a public package registry.
Attacks that exploit this kind of access
The rule that runs crates_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crates_search, this is the rule to start with:
crates_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every crates_search call is checked against it from then on.
Questions about crates_search
Search Rust crates on crates.io by name or keyword. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
crates_search accepts 2 parameters: query, per_page. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for crates_search: 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 UnClick. Nothing to install.
crates_search 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 crates_search 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 crates_search. 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.
crates_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue