cli_docker_up · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_docker_up does on LaunchFrame MCP

AI agents invoke cli_docker_up 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_up needs a policy

This tool triggers external system operations (starting Docker containers) that affect the runtime environment. While not destructive (containers can be stopped), and not directly damaging data, it executes commands whose side effects depend on the project's Docker configuration and cannot be fully predicted without knowing what services are defined.

From the tool's definition "Start Docker services" indicates launching containerized processes; "Always runs detached (background)" confirms execution of external operations whose effects depend on runtime configuration and project state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_docker_up Rate-limited

cli_docker_up 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_up": {
      "limits": [
        {
          "counter": "cli_docker_up_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_up

What does the cli_docker_up tool do? +

Start Docker services for a LaunchFrame project. Always runs detached (background). Use cli_docker_logs to inspect output afterward. 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_up? +

Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_docker_up: 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_up? +

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

Can I rate-limit cli_docker_up? +

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

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

cli_docker_up 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.