List environments in a project
AI agents call list_environments to retrieve information from Coolify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing environments without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation that retrieves information from the Coolify instance. While the server overall manages critical infrastructure, this specific tool poses minimal risk as it only exposes existing configuration data without enabling changes or deployments.
From the tool's definition Tool name 'list_environments' and description 'List environments in a project' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List environments in a project. It is categorised as a Read tool in the Coolify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for list_environments: 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 MCP Server. Nothing to install.
list_environments 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 list_environments 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 list_environments. 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.
list_environments is provided by the Coolify MCP Server MCP server (kof70/coolify-mcp-server). 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 →