dokploy_remove_volume_backup

Delete a volume backup configuration. Does not delete previously created backup files at the destination.

Server Dokploy wyattjoh/dokploy-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What dokploy_remove_volume_backup does on Dokploy

AI agents call dokploy_remove_volume_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.

Why dokploy_remove_volume_backup needs a policy

This tool permanently deletes a volume backup configuration, which cannot be undone. While the description clarifies that previously created backup files are not deleted, the removal of the backup configuration itself is an irreversible operation that eliminates the ability to restore from that backup point going forward. This qualifies as Destructive rather than Write (which is reversible).

From the tool's definition Tool name contains 'remove' and description states 'Delete a volume backup configuration.' The verb 'delete' combined with removal of backup data indicates irreversible deletion.

Questions about dokploy_remove_volume_backup

What does the dokploy_remove_volume_backup tool do? +

Delete a volume 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.

How do I enforce a policy on dokploy_remove_volume_backup? +

Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_remove_volume_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.

What risk level is dokploy_remove_volume_backup? +

dokploy_remove_volume_backup is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit dokploy_remove_volume_backup? +

Yes. Add a rate_limit block to the dokploy_remove_volume_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.

How do I block dokploy_remove_volume_backup completely? +

Set action: deny in the PolicyLayer policy for dokploy_remove_volume_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.

What MCP server provides dokploy_remove_volume_backup? +

dokploy_remove_volume_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.