compose-build

What compose-build does on Search

AI agents invoke compose-build to trigger actions in Search. 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 compose-build is rated High

This tool triggers external operations (Docker image builds) whose effects depend on the Dockerfile contents and build arguments. While the output is structured status information, the action itself executes code in the build context. This falls under Execute rather than Write because it runs commands/triggers operations whose side effects are determined by external artifacts (Dockerfiles), not just data creation.

From the tool's definition Tool description states it 'Builds Docker Compose service images', which involves executing the docker-compose build command. Building container images executes code from Dockerfiles and can run arbitrary build steps.

The rule that runs compose-build safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Search, 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:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compose-build": {
      "limits": [
        {
          "counter": "compose-build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about compose-build