Get resource usage statistics for all running containers.
AI agents call docker_get_stats to retrieve information from HomeOps 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 container statistics (CPU, memory, network I/O) for observability purposes. It performs no mutations, executions, or side effects—only data retrieval. The sibling tools (docker_list_containers, docker_get_logs, emby_get_sessions, emby_search_library) are all Read operations, consistent with this classification. Misuse by an AI agent would only expose resource metrics, not modify infrastructure.
From the tool's definition Tool name 'docker_get_stats' and description 'Get resource usage statistics for all running containers' indicate a read-only operation that retrieves monitoring data without modifying state.
Attacks that exploit this kind of access
Get resource usage statistics for all running containers. It is categorised as a Read tool in the HomeOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HomeOps MCP Server MCP server in PolicyLayer and add a rule for docker_get_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 HomeOps MCP Server. Nothing to install.
docker_get_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 docker_get_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 docker_get_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.
docker_get_stats is provided by the HomeOps MCP Server MCP server (wolffcatskyy/homeops-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 →