获取容器资源使用统计
AI agents call get_container_stats to retrieve information from ContainerGuard MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply queries and returns container resource statistics (CPU, memory, disk usage, etc.). It has no side effects, makes no modifications to the system, and poses minimal risk if misused by an agent—it only exposes operational metrics already available through standard Docker API read operations.
From the tool's definition Tool name 'get_container_stats' and description '获取容器资源使用统计' (retrieve container resource usage statistics) indicate a data retrieval operation. The function retrieves monitoring metrics about containers without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
获取容器资源使用统计. It is categorised as a Read tool in the ContainerGuard MCP MCP Server, which means it retrieves data without modifying state.
Register the ContainerGuard MCP server in PolicyLayer and add a rule for get_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 ContainerGuard MCP. Nothing to install.
get_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 get_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 get_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.
get_container_stats is provided by the ContainerGuard MCP server (rockmelodies/containerguardmcp). 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 →