crates_get

Get detailed info for a Rust crate by name from crates.io.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/crates-get.md

WHAT IT DOES

What crates_get does on UnClick

AI agents call crates_get 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
`name`	string	Yes	Crate name.

Parameters from the server's own tool schema.

RISK

Why crates_get is rated Low

This tool queries crates.io to retrieve metadata and information about a Rust crate. It performs a lookup operation with no capability to modify, delete, or execute code. It merely returns information about publicly available package metadata. The blast radius of misuse is minimal - an agent could retrieve crate information repeatedly but cannot cause damage or side effects.

From the tool's definition Tool description states 'Get detailed info for a Rust crate by name from crates.io' - 'Get' and 'detailed info' indicate read-only retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crates_get 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_get, this is the rule to start with:

crates_get Allowed

crates_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crates_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every crates_get call is checked against it from then on.

FAQ

Questions about crates_get

What does the crates_get tool do? +

Get detailed info for a Rust crate by name from crates.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does crates_get accept? +

crates_get accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on crates_get? +

Register the UnClick MCP server in PolicyLayer and add a rule for crates_get: 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.

What risk level is crates_get? +

crates_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crates_get? +

Yes. Add a rate_limit block to the crates_get 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.

How do I block crates_get completely? +

Set action: deny in the PolicyLayer policy for crates_get. 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.

What MCP server provides crates_get? +

crates_get 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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →