dokploy_trigger_volume_backup · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_trigger_volume_backup does on Dokploy

AI agents invoke dokploy_trigger_volume_backup to trigger actions in Dokploy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why dokploy_trigger_volume_backup needs a policy

This tool triggers execution of a backup operation immediately, bypassing normal scheduling. This fits the Execute category as it runs an operation whose side effects depend on arguments (which volume to back up). Severity is high because a misconfigured or malicious trigger could consume significant resources, potentially causing denial of service or data exposure if backup credentials/targets are compromised.

From the tool's definition Tool performs an immediate operation: 'Run a volume backup now, ignoring its schedule.' This is an action that triggers an external operation (a backup process) whose effects depend on the volume being backed up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_trigger_volume_backup Rate-limited

dokploy_trigger_volume_backup stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_trigger_volume_backup": {
      "limits": [
        {
          "counter": "dokploy_trigger_volume_backup_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_trigger_volume_backup

What does the dokploy_trigger_volume_backup tool do? +

Run a volume backup now, ignoring its schedule. It is categorised as a Execute tool in the Dokploy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dokploy_trigger_volume_backup? +

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

dokploy_trigger_volume_backup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dokploy_trigger_volume_backup? +

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

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

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