Get real-time resource usage statistics for a container (CPU, memory, network, I/O)
AI agents call container_stats 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 queries and retrieves monitoring data about container resource consumption. It is a read-only operation that has no side effects—it neither modifies container state, executes code within containers, nor affects infrastructure. The data retrieved is informational only, making it appropriate for the Read category with low severity risk.
From the tool's definition Tool name 'container_stats' and description indicate it retrieves real-time resource usage statistics (CPU, memory, network, I/O) for a container with no mention of modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get real-time resource usage statistics for a container (CPU, memory, network, I/O). 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 container_stats: 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.
container_stats 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 container_stats 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 container_stats. 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.
container_stats 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 →