clippy
Runs cargo clippy and returns structured lint diagnostics.
This record as markdown: /tools/io-github-dave-london-docker/clippy.md
What clippy does on Docker
AI agents invoke clippy to trigger actions in Docker. 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 clippy is rated High
The tool executes a cargo clippy command (a Rust linter) against code, which involves running an external process/build tool. While primarily for analysis, it executes code in the environment and could trigger compilation and execution of build scripts. The blast radius is medium as it runs arbitrary project code during linting but doesn't modify or delete data.
From the tool's definition Runs cargo clippy
Attacks that exploit this kind of access
The rule that runs clippy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clippy, this is the rule to start with:
clippy 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 Docker, apply this rule, and every clippy call is checked against it from then on.
Questions about clippy
Runs cargo clippy and returns structured lint diagnostics. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docker MCP server in PolicyLayer and add a rule for clippy: 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 Docker. Nothing to install.
clippy 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 clippy 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 clippy. 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.
clippy is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
Across the catalogue