cli_module_add · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_module_add does on LaunchFrame MCP

AI agents invoke cli_module_add 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_module_add needs a policy

This tool executes a multi-step operation: it installs a module, rebuilds Docker containers, and restarts the application stack. These are external system operations with significant side effects (container rebuilds, stack restarts). The 'non-interactively (skips confirmation)' note means no human approval gate exists.

From the tool's definition 'Install a module into a LaunchFrame project. Runs non-interactively (skips confirmation). Rebuilds affected containers and restarts the stack in detached mode.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_module_add Rate-limited

cli_module_add 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_module_add": {
      "limits": [
        {
          "counter": "cli_module_add_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_module_add

What does the cli_module_add tool do? +

Install a module into a LaunchFrame project. Runs non-interactively (skips confirmation). Rebuilds affected containers and restarts the stack in detached mode. 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_module_add? +

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

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

Can I rate-limit cli_module_add? +

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

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

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