Remove a Docker container
AI agents call docker_remove_container to permanently remove resources in Cargoshipper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a Docker container is a destructive operation that cannot be undone—it permanently deletes the container and its state (unless a backup/image exists separately). While the underlying image may persist, the running instance and its data are irrevocably removed. This poses high blast radius if an AI agent targets the wrong container, potentially disrupting services or losing transient data.
From the tool's definition Tool name 'docker_remove_container' with description 'Remove a Docker container' indicates irreversible deletion of container resources.
Attacks that exploit this kind of access
Remove a Docker container. It is categorised as a Destructive tool in the Cargoshipper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cargoshipper MCP server in PolicyLayer and add a rule for docker_remove_container: 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 Cargoshipper. Nothing to install.
docker_remove_container 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 docker_remove_container 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 docker_remove_container. 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.
docker_remove_container is provided by the Cargoshipper MCP server (scarr7981/cargoshipper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →