cli_docker_build · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_docker_build does on LaunchFrame MCP

AI agents invoke cli_docker_build to trigger actions in LaunchFrame MCP. 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 IT NEEDS A POLICY

Why cli_docker_build needs a policy

Building Docker images is a form of code execution—it triggers a Docker daemon process that compiles application code and creates container images. While not immediately destructive, the action has side effects (consuming compute resources, potentially overwriting existing images) and depends on arguments for scope.

From the tool's definition The tool performs 'Build Docker images' which is an external operation that executes the Docker build process. This is a code execution action triggered by the tool's arguments (selecting which services to build).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_docker_build Rate-limited

cli_docker_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": {
    "cli_docker_build": {
      "limits": [
        {
          "counter": "cli_docker_build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LaunchFrame MCP, so you can run agents against it safely.

FAQ

Questions about cli_docker_build

What does the cli_docker_build tool do? +

Build Docker images for a LaunchFrame project (all services or a specific one). It is categorised as a Execute tool in the LaunchFrame MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cli_docker_build? +

Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_docker_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 LaunchFrame MCP. Nothing to install.

What risk level is cli_docker_build? +

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

Can I rate-limit cli_docker_build? +

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

Set action: deny in the PolicyLayer policy for cli_docker_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 cli_docker_build? +

cli_docker_build is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.