docker_build

What docker_build does on Code MCP Server

AI agents invoke docker_build to trigger actions in Code MCP Server. 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 docker_build is rated High

Docker image building is code execution—it runs instructions defined in a Dockerfile that could include shell commands, package installations, and arbitrary operations. While the blast radius is contained to a single image build (not system-wide), the tool can execute potentially harmful commands embedded in a Dockerfile and consume system resources. This justifies 'Execute' rather than lower categories.

From the tool's definition Tool description states: 'Build a Docker image from a Dockerfile'. Building a Docker image executes the Dockerfile instructions, which can run arbitrary code within a container context. The server description also confirms 'Docker integration' capabilities.

The rule that runs docker_build safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker_build": {
      "limits": [
        {
          "counter": "docker_build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about docker_build