Get detailed information about a container
AI agents call docker_inspect to retrieve information from MCP Container Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
docker_inspect is a standard Docker introspection command that queries and returns container configuration, status, and metadata. It has no side effects, does not execute code or commands within the container, does not modify container state, and does not delete resources. This is a straightforward Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'docker_inspect' and description 'Get detailed information about a container' indicate a read-only operation that retrieves container metadata and state without modifying or executing anything.
Attacks that exploit this kind of access
Get detailed information about a container. It is categorised as a Read tool in the MCP Container Tools MCP Server, which means it retrieves data without modifying state.
Register the MCP Container Tools MCP server in PolicyLayer and add a rule for docker_inspect: 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 Container Tools. Nothing to install.
docker_inspect 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_inspect 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_inspect. 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_inspect is provided by the MCP Container Tools MCP server (simseksem/mcp-container-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →