Remove a Docker image
AI agents call remove_image to permanently remove resources in Docker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a Docker image permanently deletes the image from the local Docker repository. This operation cannot be reversed without rebuilding or re-pulling the image. While not as critical as deleting data, it represents irreversible destruction of a system artifact. The high severity reflects that an agent could mistakenly remove production images, breaking deployments.
From the tool's definition Tool name 'remove_image' combined with description 'Remove a Docker image' indicates irreversible deletion of Docker images. The verb 'remove' in Docker context is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Remove a Docker image. It is categorised as a Destructive tool in the Docker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Docker MCP Server MCP server in PolicyLayer and add a rule for remove_image: 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 MCP Server. Nothing to install.
remove_image 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 remove_image 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 remove_image. 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.
remove_image is provided by the Docker MCP Server MCP server (swartdraak/docker-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 →