Critical Risk →

compose-down

Stops Docker Compose services and returns structured status.

How to control compose-down ↓

What compose-down does on Make

AI agents call compose-down to permanently remove resources in Make — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why compose-down needs a policy

'docker compose down' stops and removes containers, networks, and optionally volumes. This is not easily reversible — running services are terminated and their associated resources are torn down. The blast radius is high because it can take down entire application stacks in production environments.

From the tool's definition compose-down — 'Stops Docker Compose services'

Documented attack patterns abuse exactly the kind of access compose-down gives an agent:

How to control compose-down

PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for compose-down:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "compose-down"
  ]
}

compose-down disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about compose-down

What does the compose-down tool do? +

Stops Docker Compose services and returns structured status. It is categorised as a Destructive tool in the Make MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

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

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

What risk level is compose-down? +

compose-down is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit compose-down? +

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

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

compose-down is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Make tool call.

Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.