AI agents call docker_get_containers 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 queries container information (listing/fetching containers) without modifying, executing, or deleting anything. It is purely informational and has minimal blast radius if misused by an AI agent — worst case is information disclosure about running containers. This aligns with the 'Read' category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool description states 'Get containers on a specific host' — a retrieval operation with no modification or execution capability. The verb 'Get' and the read-only nature of querying container status indicate no side effects.
Attacks that exploit this kind of access
Get containers on a specific host (works with both Docker and Podman). 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 docker_get_containers: 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.
docker_get_containers 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_containers 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_containers. 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_containers 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 →