black
Runs Black code formatter and returns structured results (files changed, unchanged, would reformat).
This record as markdown: /tools/io-github-dave-london-cargo/black.md
What black does on Cargo
AI agents invoke black to trigger actions in Cargo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why black is rated High
Black actively reformats source files on disk, modifying their contents. This is a write/execute operation — it runs an external tool that changes files. Since it modifies files in place (potentially irreversibly overwriting formatting), it falls under Execute (running an external process with side effects on the filesystem).
From the tool's definition Runs Black code formatter and returns structured results (files changed, unchanged, would reformat)
Attacks that exploit this kind of access
The rule that runs black 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 black, this is the rule to start with:
black stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 black call is checked against it from then on.
Questions about black
Runs Black code formatter and returns structured results (files changed, unchanged, would reformat). It is categorised as a Execute tool in the Cargo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cargo MCP server in PolicyLayer and add a rule for black: 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.
black is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the black 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 black. 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.
black 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.
Across the catalogue