AI agents call docker_find_containers_by_label 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 or queries container data based on labels without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, matching the Read category definition. The blast radius is minimal—worst case, an AI agent learns which containers exist with certain labels. Severity is low because there are no destructive, financial, or code-execution implications.
From the tool's definition The tool name contains 'find' and description states 'Find containers by label key-value pair', indicating a query/search operation with no data modification or system impact.
Attacks that exploit this kind of access
Find containers by label key-value pair (e.g., find traefik-enabled containers or containers with specific domains). 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_find_containers_by_label: 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_find_containers_by_label 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_find_containers_by_label 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_find_containers_by_label. 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_find_containers_by_label 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 →