dokploy_stop_compose · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_stop_compose does on Dokploy

AI agents invoke dokploy_stop_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_stop_compose needs a policy

This tool executes a command that stops a running Docker Compose stack, which is an operational action with immediate infrastructure impact. It is reversible (the stack can be restarted), so it does not qualify as Destructive. The action depends on which compose stack is specified as an argument and will have real-world effects on deployed services.

From the tool's definition Tool name 'dokploy_stop_compose' and description 'Stop a running compose stack' indicate execution of a control operation that triggers external effects on infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_stop_compose Rate-limited

dokploy_stop_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_stop_compose": {
      "limits": [
        {
          "counter": "dokploy_stop_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_stop_compose

What does the dokploy_stop_compose tool do? +

Stop a running 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_stop_compose? +

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

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

Can I rate-limit dokploy_stop_compose? +

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

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

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