Delete a backup configuration. Does not delete previously created backup files at the destination.
AI agents call dokploy_remove_backup to permanently remove resources in Dokploy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes backup configurations, which cannot be undone. While the description notes that actual backup files at the destination are preserved, the deletion of the backup configuration itself is an irreversible action that removes infrastructure configuration. This fits the Destructive category as it represents data that, once removed, cannot be recovered through normal means.
From the tool's definition Tool name contains 'remove_backup' and description explicitly states 'Delete a backup configuration'. The verb 'Delete' combined with removal of backup configurations indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a backup configuration. Does not delete previously created backup files at the destination. It is categorised as a Destructive tool in the Dokploy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_remove_backup: 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 Dokploy. Nothing to install.
dokploy_remove_backup 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 dokploy_remove_backup 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 dokploy_remove_backup. 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.
dokploy_remove_backup is provided by the Dokploy MCP server (wyattjoh/dokploy-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 →