AI agents call docker_get_all_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 retrieves container metadata/state across a homelab infrastructure. It performs no side effects, creates no resources, modifies nothing, and executes no code. It is a straightforward informational query analogous to 'docker ps' or 'list containers'. The blast radius of misuse is low—an AI agent gaining this capability cannot damage systems, only view existing container configurations and states.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get all containers across all hosts' — it queries and lists Docker containers without modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get all containers across all hosts. 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_all_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_all_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_all_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_all_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_all_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 →