dokploy_create_compose_backup · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_create_compose_backup does on Dokploy

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

This tool creates a backup resource with scheduled execution, which is a reversible write operation (backups can be deleted/modified). It requires database credentials ('metadata carries the credentials needed') suggesting it has significant privilege and could impact data protection mechanisms.

From the tool's definition Tool creates a scheduled backup, which involves persisting a new backup configuration/resource in the system. The description states 'Create a scheduled backup' which is a write operation that modifies system state by adding a new backup resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_create_compose_backup Rate-limited

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

What does the dokploy_create_compose_backup tool do? +

Create a scheduled backup for a database running inside a compose stack. databaseType selects which DB inside the stack is being backed up (postgres/mariadb/mysql/mongo). metadata carries the credentials needed to dump that DB. 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_backup? +

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

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

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

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

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