This record as markdown: /tools/coolify/delete-service.md
What delete_service does on Coolify
AI agents call delete_service 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_service is rated Critical
This tool permanently removes a service from the Coolify deployment platform. Deletion is irreversible and represents the most severe category of risk. An AI agent misusing this could eliminate critical application services, causing complete system outage and data loss. The high-confidence classification reflects explicit destructive language in both the tool name and description.
From the tool's definition Tool named 'delete_service' with description 'Delete a service by UUID.' The verb 'Delete' indicates irreversible removal of data/resources.
Attacks that exploit this kind of access
The rule that runs delete_service 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_service, this is the rule to start with:
delete_service 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_service call is checked against it from then on.
Questions about delete_service
Delete a service 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_service: 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_service 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_service 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_service. 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_service 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