AI agents call docker_compose_status to retrieve information from Infra Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the current state of Docker Compose services. It performs no writes, deletions, code execution, or financial operations—it is a pure read/query operation. The 'Get' verb and focus on 'status' and 'states' confirm read-only behavior. Severity is low as misuse would only expose operational status information, not enable resource modification or data loss.
From the tool's definition Tool name 'docker_compose_status' and description 'Get Docker Compose project status showing all services and their states' indicate a query operation that retrieves status information without modifying infrastructure.
Attacks that exploit this kind of access
Get Docker Compose project status showing all services and their states. It is categorised as a Read tool in the Infra Ops MCP Server, which means it retrieves data without modifying state.
Register the Infra Ops MCP server in PolicyLayer and add a rule for docker_compose_status: 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 Ops. Nothing to install.
docker_compose_status 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_compose_status 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_compose_status. 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_compose_status is provided by the Infra Ops MCP server (skyvanguard/infra-ops-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 →