Manage environments: list/get/create/delete (get includes dragonfly/keydb/clickhouse DBs missing from API)
AI agents call environments to permanently remove resources in Coolify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool supports delete operations on environments, which are infrastructure-level containers. Deleting an environment could irreversibly remove all associated applications, databases, and configurations. Per the severity rules, Destructive takes precedence over Write (create) and Read (list/get).
From the tool's definition Manage environments: list/get/create/delete — the 'delete' operation is explicitly listed and environments are likely top-level containers for applications and databases, making deletion irreversible and high-impact.
Attacks that exploit this kind of access
Manage environments: list/get/create/delete (get includes dragonfly/keydb/clickhouse DBs missing from API). It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP server in PolicyLayer and add a rule for 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. Nothing to install.
environments is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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 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.
environments 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 →