Get detailed information about a container
AI agents call inspect_container to retrieve information from Docker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata and status information about a Docker container. It does not create, modify, delete, or execute any operations on the container or other resources. The read-only nature of inspection operations means there is minimal risk of unintended consequences from misuse—the worst outcome would be information disclosure about container state.
From the tool's definition Tool name 'inspect_container' and description 'Get detailed information about a container' indicate a query/retrieval operation with no side effects. The verb 'get' and 'inspect' are characteristic of Read category tools.
Attacks that exploit this kind of access
Get detailed information about a container. It is categorised as a Read tool in the Docker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Docker MCP Server MCP server in PolicyLayer and add a rule for inspect_container: 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 MCP Server. Nothing to install.
inspect_container 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 inspect_container 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 inspect_container. 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.
inspect_container is provided by the Docker MCP Server MCP server (swartdraak/docker-mcp). 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 →