deploy-compose · Docker MCP: Risk & Policy

WHAT IT DOES

What deploy-compose does on Docker

AI agents invoke deploy-compose to trigger actions in Docker. 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 deploy-compose needs a policy

This tool triggers external operations (Docker daemon commands) that instantiate and configure running services. While not immediately destructive (containers can be stopped), the deployment itself has significant side effects: network creation, volume allocation, service initialization, and resource consumption. Misuse could spawn unintended services, expose ports, or allocate resources maliciously.

From the tool's definition Tool name 'deploy-compose' and description 'Deploy a Docker Compose stack' indicate execution of infrastructure operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy-compose Rate-limited

deploy-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": {
    "deploy-compose": {
      "limits": [
        {
          "counter": "deploy-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 Docker, so you can run agents against it safely.

FAQ

Questions about deploy-compose

What does the deploy-compose tool do? +

Deploy a Docker Compose stack. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy-compose? +

Register the Docker MCP server in PolicyLayer and add a rule for deploy-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 Docker. Nothing to install.

What risk level is deploy-compose? +

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

Can I rate-limit deploy-compose? +

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

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

deploy-compose is provided by the Docker MCP server (quantgeekdev/docker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.