compose-build

Builds Docker Compose service images and returns structured per-service build 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-build.md

WHAT IT DOES

What compose-build does on Git

AI agents invoke compose-build 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-build is rated High

This tool triggers external command execution (docker-compose build) that constructs container images. While the operation is reversible in principle (images can be deleted), the execution of arbitrary build contexts and Dockerfiles from untrusted sources could result in malicious code execution, data exfiltration, or system compromise.

From the tool's definition Tool name 'compose-build' and description 'Builds Docker Compose service images' indicates execution of Docker Compose build operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compose-build 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-build, this is the rule to start with:

compose-build Rate-limited

compose-build 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-build": {
      "limits": [
        {
          "counter": "compose-build_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-build call is checked against it from then on.

FAQ

Questions about compose-build

What does the compose-build tool do? +

Builds Docker Compose service images and returns structured per-service build 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-build? +

Register the Git MCP server in PolicyLayer and add a rule for compose-build: 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-build? +

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

Can I rate-limit compose-build? +

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

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

compose-build 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 →