Critical-risk tools in Docker
10 of the 56 tools in Docker are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
docker_compose_downDestructive 4/5Stop and remove Docker Compose services
-
docker_prune_containersDestructive 4/5Remove stopped containers. Requires confirmation for safety. First call without confirm to see what will be removed, then call again with confirm=true to proceed.
-
docker_prune_imagesDestructive 4/5Remove unused images. Requires confirmation for safety. First call without confirm to see what will be removed, then call again with confirm=true to proceed.
-
docker_prune_networksDestructive 4/5Remove unused networks. Requires confirmation for safety. First call without confirm to see what will be removed, then call again with confirm=true to proceed.
-
docker_prune_systemDestructive 4/5Remove unused data (containers, networks, images, build cache). Requires confirmation for safety. First call without confirm to see what will be removed, then call again with co...
-
docker_prune_volumesDestructive 4/5Remove unused volumes. Requires confirmation for safety. First call without confirm to see what will be removed, then call again with confirm=true to proceed.
-
docker_remove_containerDestructive 4/5Remove a container. Requires confirmation for safety. First call without confirm to see container details, then call again with confirm=true to proceed.
-
docker_remove_imageDestructive 4/5Remove an image. Requires confirmation for safety. First call without confirm to see image details, then call again with confirm=true to proceed.
-
docker_remove_networkDestructive 4/5Remove a Docker network. Requires confirmation for safety. First call without confirm to see network details, then call again with confirm=true to proceed.
-
docker_remove_volumeDestructive 4/5Remove a Docker volume. Requires confirmation for safety. First call without confirm to see volume details, then call again with confirm=true to proceed. Alternatively, uses MCP...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Docker
Enforce policy on Docker
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init