cargo_crate
Look up a Rust crate on crates.io: latest version, description, total downloads, repository, and homepage. Keyless.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cargo-crate.md
What cargo_crate does on Livedatalink
AI agents call cargo_crate to retrieve information from Livedatalink 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, e.g. 'serde'. |
Parameters from the server's own tool schema.
Why cargo_crate is rated Low
This tool performs a read-only lookup of public Rust package metadata. It retrieves information without modifying, deleting, or executing any code. The keyless access indicates it's a simple public data query. No financial, destructive, or execution capabilities are present.
From the tool's definition Tool description states it 'Look[s] up' information and retrieves metadata fields: 'latest version, description, total downloads, repository, and homepage.' These are read-only queries against crates.io with no side effects.
Attacks that exploit this kind of access
The rule that runs cargo_crate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cargo_crate, this is the rule to start with:
cargo_crate 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 Livedatalink, apply this rule, and every cargo_crate call is checked against it from then on.
Questions about cargo_crate
Look up a Rust crate on crates.io: latest version, description, total downloads, repository, and homepage. Keyless. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cargo_crate accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for cargo_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 Livedatalink. Nothing to install.
cargo_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 cargo_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 cargo_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.
cargo_crate is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue