audit
Runs cargo audit and returns structured vulnerability data.
This record as markdown: /tools/io-github-dave-london-cargo/audit.md
What audit does on Cargo
AI agents call audit to retrieve information from Cargo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why audit is rated Low
The cargo audit command is a dependency vulnerability scanner that queries the advisory database and reports findings. It produces no side effects—no code is modified, no dependencies are installed or changed, and no system state is altered. This is purely informational retrieval, making it a Read category tool.
From the tool's definition Tool name 'audit' and description 'Runs cargo audit and returns structured vulnerability data' indicate a read-only operation that scans and reports vulnerabilities without modifying code, dependencies, or system state.
Attacks that exploit this kind of access
The rule that runs audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit, this is the rule to start with:
audit 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 Cargo, apply this rule, and every audit call is checked against it from then on.
Questions about audit
Runs cargo audit and returns structured vulnerability data. It is categorised as a Read tool in the Cargo MCP Server, which means it retrieves data without modifying state.
Register the Cargo MCP server in PolicyLayer and add a rule for audit: 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 Cargo. Nothing to install.
audit 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 audit 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 audit. 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.
audit is provided by the Cargo MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cargo, and thousands of servers like it.
This server
Across the catalogue