dokploy_update_compose · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_update_compose does on Dokploy

AI agents use dokploy_update_compose 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_update_compose needs a policy

This tool modifies compose stack configuration, which is a Write operation (creates or modifies data reversibly). Severity is high because misconfigured compose stacks can impact deployed applications, services, and infrastructure—an AI agent could introduce breaking changes to production services.

From the tool's definition Tool name 'dokploy_update_compose' and description 'Update compose stack config fields' explicitly indicate modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_update_compose Rate-limited

dokploy_update_compose 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_update_compose": {
      "limits": [
        {
          "counter": "dokploy_update_compose_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_update_compose

What does the dokploy_update_compose tool do? +

Update compose stack config fields. Only composeId is required; all other fields are optional. 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_update_compose? +

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

dokploy_update_compose is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dokploy_update_compose? +

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

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

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