hadolint
Runs Hadolint (Dockerfile linter) and returns structured diagnostics (file, line, rule, severity, message).
This record as markdown: /tools/io-github-dave-london-cargo/hadolint.md
What hadolint does on Cargo
AI agents invoke hadolint 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 hadolint is rated High
The tool executes an external linting process (Hadolint) against Dockerfile(s). While it only reads and analyzes files rather than modifying them, it actively runs an external binary/process, placing it in the Execute category. Severity is medium because misuse could involve pointing it at unintended files or consuming resources, though its blast radius is limited since it only produces diagnostics.
From the tool's definition Runs Hadolint (Dockerfile linter)
Attacks that exploit this kind of access
The rule that runs hadolint 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 hadolint, this is the rule to start with:
hadolint 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 hadolint call is checked against it from then on.
Questions about hadolint
Runs Hadolint (Dockerfile linter) and returns structured diagnostics (file, line, rule, severity, message). 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 hadolint: 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.
hadolint 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 hadolint 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 hadolint. 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.
hadolint 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