AI agents call infra_status_tool to retrieve information from Infra without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of running containers in a Docker Compose stack and returns information. It performs no modifications, deletions, or external operations. The blast radius of misuse is minimal—an agent could only retrieve infrastructure status information, not alter or harm systems. Confidence is high because the description clearly indicates a list/read operation with no capability to modify state.
From the tool's definition Tool description states 'List every container' — a retrieval operation with no side effects. The verb 'list' and the read-only nature of querying container state confirm this is a Read category tool.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every container in the compose stack with state + status string. It is categorised as a Read tool in the Infra MCP Server, which means it retrieves data without modifying state.
Register the Infra MCP server in PolicyLayer and add a rule for infra_status_tool: 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 Infra. Nothing to install.
infra_status_tool 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 infra_status_tool 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 infra_status_tool. 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.
infra_status_tool is provided by the Infra MCP server (odanree/infra-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 →