dokploy_create_compose_volume_backup

WHAT IT DOES

What dokploy_create_compose_volume_backup does on Dokploy

AI agents use dokploy_create_compose_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_create_compose_volume_backup needs a policy

The tool creates a new backup schedule/resource, which is a reversible write operation. While backups protect data, creating a backup schedule itself is a non-destructive modification that can be updated or removed. Severity is medium because misconfiguration could impact disaster recovery capabilities, but the action itself is not irreversible or immediately damaging.

From the tool's definition Tool name contains 'create' and description states 'Create a scheduled volume backup for a service'. This creates a new backup configuration resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_create_compose_volume_backup Rate-limited

dokploy_create_compose_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_create_compose_volume_backup": {
      "limits": [
        {
          "counter": "dokploy_create_compose_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_create_compose_volume_backup

What does the dokploy_create_compose_volume_backup tool do? +

Create a scheduled volume backup for a service inside a compose stack. serviceName identifies which service in the compose file owns the volume. 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_create_compose_volume_backup? +

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

dokploy_create_compose_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_create_compose_volume_backup? +

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

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

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