dokploy_update_volume_backup · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_update_volume_backup does on Dokploy

AI agents use dokploy_update_volume_backup to create or update resources in Dokploy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dokploy environment.

WHY IT NEEDS A POLICY

Why dokploy_update_volume_backup needs a policy

This tool creates or modifies backup configuration data in a reversible manner. While high severity due to the potential impact of misconfigured backups (which could affect disaster recovery), it does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or trigger deployments (Execute). The primary action is configuration modification, making it Write category.

From the tool's definition Tool name contains 'update' and description states 'Update a volume backup configuration' — this modifies existing backup settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_update_volume_backup Rate-limited

dokploy_update_volume_backup stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dokploy_update_volume_backup": {
      "limits": [
        {
          "counter": "dokploy_update_volume_backup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dokploy, so you can run agents against it safely.

FAQ

Questions about dokploy_update_volume_backup

What does the dokploy_update_volume_backup tool do? +

Update a volume backup configuration. Fetch the current config with dokploy_get_volume_backup first, then send the merged result so existing fields are preserved. serviceName is required for compose backups; pass an empty string for application backups. It is categorised as a Write tool in the Dokploy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dokploy_update_volume_backup? +

Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_update_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_update_volume_backup? +

dokploy_update_volume_backup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dokploy_update_volume_backup? +

Yes. Add a rate_limit block to the dokploy_update_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_update_volume_backup completely? +

Set action: deny in the PolicyLayer policy for dokploy_update_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_update_volume_backup? +

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