Manage backups: list_schedules/get_schedule/list_executions/get_execution/delete_execution/create/update/delete
AI agents call database_backups 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.
While the tool offers read operations (list_schedules, get_schedule, list_executions, get_execution) and write operations (create, update), the presence of destructive operations (delete, delete_execution) elevates it to the Destructive category per the severity hierarchy. An AI agent with access to this tool could permanently destroy backup data, preventing recovery from incidents.
From the tool's definition Tool includes 'delete' and 'delete_execution' operations on backups, which irreversibly removes backup data. Backups are critical recovery mechanisms; deleting them cannot be undone and eliminates disaster recovery options.
Attacks that exploit this kind of access
Manage backups: list_schedules/get_schedule/list_executions/get_execution/delete_execution/create/update/delete. 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 database_backups: 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.
database_backups 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 database_backups 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 database_backups. 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.
database_backups 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 →