AI agents call get_infrastructure_overview to retrieve information from Coolify 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 query of infrastructure state, returning informational counts and overview data. It has no side effects, cannot modify or delete resources, and does not trigger external operations. Misuse by an AI agent would only result in information disclosure of infrastructure topology, which is a low-severity risk.
From the tool's definition Tool name 'get_infrastructure_overview' and description 'Overview of all resources with counts' indicate a retrieval/query operation that returns aggregate statistics and resource counts without modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Overview of all resources with counts. It is categorised as a Read tool in the Coolify MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP server in PolicyLayer and add a rule for get_infrastructure_overview: 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 Coolify. Nothing to install.
get_infrastructure_overview 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 get_infrastructure_overview 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 get_infrastructure_overview. 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.
get_infrastructure_overview is provided by the Coolify MCP server (jurislm/coolify-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 →