compose-down

Stops Docker Compose services and returns structured status.

SERVERGit SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/compose-down.md

WHAT IT DOES

What compose-down does on Git

AI agents invoke compose-down to trigger actions in Git. 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.

RISK

Why compose-down is rated High

Stopping Docker Compose services is an external operation that terminates running containers/services. While not permanently destructive (data volumes may persist), it halts active workloads which can have significant impact. This is an Execute-category action as it triggers external operations (stopping containers) whose effects depend on the environment.

From the tool's definition Stops Docker Compose services and returns structured status

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compose-down safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compose-down, this is the rule to start with:

compose-down Rate-limited

compose-down 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-down": {
      "limits": [
        {
          "counter": "compose-down_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every compose-down call is checked against it from then on.

FAQ

Questions about compose-down

What does the compose-down tool do? +

Stops Docker Compose services and returns structured status. It is categorised as a Execute tool in the Git 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-down? +

Register the Git 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 Git. Nothing to install.

What risk level is compose-down? +

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

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 Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →