docker_images
Manage Docker images (list, pull, push, remove, etc.)
This record as markdown: /tools/agentics-ai-code-mcp/docker-images.md
What docker_images does on Code MCP Server
AI agents invoke docker_images to trigger actions in Code MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why docker_images is rated High
This tool spans multiple categories depending on the operation: listing is Read, pulling/pushing images is Write (fetching/sending data to registries), and removing images is Destructive. Per the rules, the most severe applicable category wins.
From the tool's definition Manage Docker images (list, pull, push, remove, etc.)
Attacks that exploit this kind of access
The rule that runs docker_images safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_images, this is the rule to start with:
docker_images stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every docker_images call is checked against it from then on.
Questions about docker_images
Manage Docker images (list, pull, push, remove, etc.). It is categorised as a Execute tool in the Code MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for docker_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 Code MCP Server. Nothing to install.
docker_images is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the docker_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.
Set action: deny in the PolicyLayer policy for docker_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.
docker_images is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
Across the catalogue