AI agents call get_container_stats to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring metrics (CPU and memory statistics) from containers without modifying state, executing commands, or causing side effects. It is a read-only query operation similar to 'docker stats'. The low severity reflects that exposing container resource metrics poses minimal risk—the information is typically non-sensitive operational telemetry, and retrieval alone cannot harm the infrastructure.
From the tool's definition Tool name 'get_container_stats' and description 'Get CPU and memory stats for containers on a host' indicate data retrieval with no modification or execution of operations.
Attacks that exploit this kind of access
Get CPU and memory stats for containers on a host. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab 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 Homelab. 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 Homelab MCP server (myraffy/homelab-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 →