AI agents invoke dokploy_trigger_compose_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.
This tool executes a backup operation, which is an external action that may consume resources and modify backup storage state. While backups are generally reversible and not destructive per se, the act of triggering them is an Execute-class operation (active invocation of an external process). It does not permanently delete or overwrite data (ruling out Destructive), nor does it move money (ruling out Financial).
From the tool's definition Tool name and description indicate it 'Run a compose backup now' — actively triggers an external operation (backup process) whose effects depend on the specific compose configuration and state of the deployment.
Attacks that exploit this kind of access
Run a compose 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.
Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_trigger_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.
dokploy_trigger_compose_backup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dokploy_trigger_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.
Set action: deny in the PolicyLayer policy for dokploy_trigger_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.
dokploy_trigger_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.
dokploy_trigger_compose_backup is one line of Dokploy's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →