dokploy_start_compose · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_start_compose does on Dokploy

AI agents invoke dokploy_start_compose 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_start_compose needs a policy

Starting a compose stack executes external operations (container orchestration) with side effects that depend on the stack's configuration arguments. This is not a simple Read (no data retrieval), not a reversible Write (starting services has persistent runtime effects), and not Destructive (it doesn't delete or irreversibly overwrite).

From the tool's definition Tool name 'dokploy_start_compose' and description 'Start a stopped compose stack' indicate triggering execution of a compose stack—a Docker Compose operation that starts multiple containers and services whose behavior depends on the stack configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_start_compose Rate-limited

dokploy_start_compose 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_start_compose": {
      "limits": [
        {
          "counter": "dokploy_start_compose_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_start_compose

What does the dokploy_start_compose tool do? +

Start a stopped compose stack. 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_start_compose? +

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

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

Can I rate-limit dokploy_start_compose? +

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

Set action: deny in the PolicyLayer policy for dokploy_start_compose. 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_start_compose? +

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