compose_restart · MCP Container Tools MCP: Risk & Policy

WHAT IT DOES

What compose_restart does on MCP Container Tools

AI agents invoke compose_restart 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_restart needs a policy

This tool executes a Docker Compose command that restarts services, causing observable side effects in a live environment (downtime, state transitions). While not destructive (data is not deleted), it is Execute-class because it performs an external operation whose real-world impact depends on the arguments provided.

From the tool's definition "Restart Docker Compose services" — restarts running containers, which triggers external operations (service interruption, resource reallocation) whose effects depend on which services are specified as arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compose_restart Rate-limited

compose_restart 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_restart": {
      "limits": [
        {
          "counter": "compose_restart_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_restart

What does the compose_restart tool do? +

Restart 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_restart? +

Register the MCP Container Tools MCP server in PolicyLayer and add a rule for compose_restart: 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_restart? +

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

Can I rate-limit compose_restart? +

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

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

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