remove_image

Remove a Docker image

SERVERDocker SOURCE@ckreiling/mcp-server-docker

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/docker/remove-image.md

WHAT IT DOES

What remove_image does on Docker

AI agents call remove_image 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.

RISK

Why remove_image is rated Critical

Removing a Docker image is destructive because it permanently deletes the image from the Docker system and cannot be easily undone without rebuilding or re-pulling. While not as critical as removing running containers or volumes, image removal is irreversible and can disrupt workflows.

From the tool's definition Tool name 'remove_image' with description 'Remove a Docker image' directly indicates deletion/removal of Docker images, which is an irreversible operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_image 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 remove_image, this is the rule to start with:

remove_image Hidden

remove_image is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_image"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every remove_image call is checked against it from then on.

FAQ

Questions about remove_image

What does the remove_image tool do? +

Remove a Docker image. 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.

How do I enforce a policy on remove_image? +

Register the Docker 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. Nothing to install.

What risk level is remove_image? +

remove_image is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_image? +

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.

How do I block remove_image completely? +

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.

What MCP server provides remove_image? +

remove_image is provided by the Docker MCP server (@ckreiling/mcp-server-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 19 Docker tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →