Delete a specific backup execution
AI agents call delete_backup_execution to permanently remove resources in Coolify MCP Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly removes backup execution records. An AI agent misusing this could permanently lose recovery capabilities and data restoration options for infrastructure managed through Coolify, affecting system resilience and disaster recovery. This is a destructive operation that cannot be reversed.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific backup execution'. Backups are data recovery assets whose deletion cannot be undone.
Attacks that exploit this kind of access
Delete a specific backup execution. It is categorised as a Destructive tool in the Coolify MCP Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for delete_backup_execution: 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 Tools. Nothing to install.
delete_backup_execution 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_backup_execution 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_backup_execution. 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_backup_execution is provided by the Coolify MCP Tools MCP server (jplansink/coolify-mcp-tools). 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 →