compose_up · MCP Container Tools MCP: Risk & Policy

WHAT IT DOES

What compose_up does on MCP Container Tools

AI agents invoke compose_up to trigger actions in MCP Container Tools. 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 compose_up needs a policy

This tool triggers the execution of containerized applications and their dependencies, which qualifies as Execute rather than Write. While it doesn't delete data (not Destructive) or move money (not Financial), it initiates external operations that can have broad system effects including network exposure, resource consumption, and activation of arbitrary services defined in compose files.

From the tool's definition compose_up is a Docker Compose service startup command that executes containerized applications and external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compose_up Rate-limited

compose_up 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": {
    "compose_up": {
      "limits": [
        {
          "counter": "compose_up_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 MCP Container Tools, so you can run agents against it safely.

FAQ

Questions about compose_up

What does the compose_up tool do? +

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

How do I enforce a policy on compose_up? +

Register the MCP Container Tools MCP server in PolicyLayer and add a rule for compose_up: 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 MCP Container Tools. Nothing to install.

What risk level is compose_up? +

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

Can I rate-limit compose_up? +

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

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

compose_up is provided by the MCP Container Tools MCP server (simseksem/mcp-container-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.