docker_images
List Docker images as parsed JSON lines.
This record as markdown: /tools/mcp-control-plane/docker-images.md
What docker_images does on Mcp Control Plane
AI agents call docker_images to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why docker_images is rated Low
This tool retrieves and lists existing Docker images in JSON format. It performs no modifications, deletions, or code execution—purely an informational read operation. The blast radius is minimal; misuse would only expose information about available images, not cause operational harm or data loss.
From the tool's definition Tool name 'docker_images' and description 'List Docker images as parsed JSON lines' indicate a query/retrieval operation with no side effects.
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 Mcp Control Plane, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every docker_images call is checked against it from then on.
Questions about docker_images
List Docker images as parsed JSON lines. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane 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 Mcp Control Plane. Nothing to install.
docker_images is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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 Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue