cli_docker_down · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_docker_down does on LaunchFrame MCP

AI agents invoke cli_docker_down 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_down needs a policy

This tool stops all running Docker containers/services for a project, which is an external operational action with significant impact. While not permanently destructive (containers can be restarted), stopping all services causes immediate downtime and disrupts running workloads.

From the tool's definition Stop all running Docker services for a LaunchFrame project

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_docker_down Rate-limited

cli_docker_down 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_down": {
      "limits": [
        {
          "counter": "cli_docker_down_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_down

What does the cli_docker_down tool do? +

Stop all running Docker services for a LaunchFrame project. 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_down? +

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

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

Can I rate-limit cli_docker_down? +

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

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

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