AI agents call check_container 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 performs a read-only status check on a container. It retrieves information about whether a container is running, with no side effects, no data modification, and no irreversible actions. This is a classic Read category operation.
From the tool's definition The tool description states 'Check if a specific container is running on a host' - this is a query operation that retrieves the status of a container without modifying, deleting, or executing any operations. The action is purely informational.
Attacks that exploit this kind of access
Check if a specific container is running 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 check_container: 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.
check_container 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 check_container 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 check_container. 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.
check_container 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 →