This record as markdown: /tools/coolify/delete-server.md
What delete_server does on Coolify
AI agents call delete_server 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.
Why delete_server is rated Critical
Deletion of a server cannot be undone and will result in permanent loss of the server, its configuration, deployed applications, data, and related resources. This is the highest-impact destructive action possible in an infrastructure management system. The blast radius if misused by an AI agent is critical—an entire production environment could be destroyed.
From the tool's definition Tool name is 'delete_server' and description states 'Delete a server by UUID' — the word 'delete' combined with the scope (an entire server) indicates irreversible removal of infrastructure and all associated data.
Attacks that exploit this kind of access
The rule that runs delete_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_server, this is the rule to start with:
delete_server is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every delete_server call is checked against it from then on.
Questions about delete_server
Delete a server by UUID. 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 delete_server: 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.
delete_server 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 delete_server 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 delete_server. 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.
delete_server is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coolify, and thousands of servers like it.
Across the catalogue