Critical Risk →

docker_prune_images

Remove unused images. Requires confirmation for safety. First call without confirm to see what will be removed, then call again with confirm=true to proceed.

Part of the Docker server.

docker_prune_images can permanently delete data in Docker, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DOCKER →

Free to start. No card required.

AI agents may call docker_prune_images to permanently remove or destroy resources in Docker. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call docker_prune_images in a loop, permanently destroying resources in Docker. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "docker_prune_images"
  ]
}

See the full Docker policy for all 56 tools.

Get this rule live on your own Docker server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DOCKER →

View all 56 tools →

These attack patterns abuse exactly the kind of access docker_prune_images gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so docker_prune_images only ever does what you allow.

SECURE DOCKER →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the docker_prune_images tool do? +

Remove unused images. Requires confirmation for safety. First call without confirm to see what will be removed, then call again with confirm=true to proceed.. 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 docker_prune_images? +

Register the Docker MCP server in PolicyLayer and add a rule for docker_prune_images: 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 docker_prune_images? +

docker_prune_images 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 docker_prune_images? +

Yes. Add a rate_limit block to the docker_prune_images 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 docker_prune_images completely? +

Set action: deny in the PolicyLayer policy for docker_prune_images. 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 docker_prune_images? +

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

Enforce policy on every Docker tool call.

Deterministic rules across all 56 Docker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.