package-clean
Cleans Swift package build artifacts and returns structured result.
This record as markdown: /tools/io-github-dave-london-docker/package-clean.md
What package-clean does on Docker
AI agents call package-clean to permanently remove resources in Docker, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why package-clean is rated Critical
Cleaning build artifacts involves deleting files that were produced during the build process. While these files can typically be regenerated by rebuilding, the clean operation itself irreversibly removes them without a recovery mechanism, fitting the Destructive category. Severity is medium because only build artifacts (not source code) are affected, limiting the blast radius.
From the tool's definition 'Cleans Swift package build artifacts' — removing/deleting build artifacts is an irreversible deletion of generated files
Attacks that exploit this kind of access
The rule that runs package-clean 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 package-clean, this is the rule to start with:
package-clean is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every package-clean call is checked against it from then on.
Questions about package-clean
Cleans Swift package build artifacts and returns structured result. It is categorised as a Destructive tool in the Docker MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Docker MCP server in PolicyLayer and add a rule for package-clean: 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.
package-clean is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the package-clean 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 package-clean. 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.
package-clean 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