cli_service_add · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_service_add does on LaunchFrame MCP

AI agents use cli_service_add to create or update resources in LaunchFrame MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LaunchFrame MCP environment.

WHY IT NEEDS A POLICY

Why cli_service_add needs a policy

This tool modifies the project structure by installing services, which is a reversible write operation (services can be uninstalled or reconfigured). It does not execute arbitrary code, delete data irreversibly, or move money. While it touches infrastructure, the write happens within the project's own configuration/setup process rather than executing external commands with unpredictable side effects.

From the tool's definition Tool description states 'Install an optional service into a LaunchFrame project' — this creates or adds infrastructure components to the project. The name 'cli_service_add' and verb 'Install' indicate a modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_service_add Rate-limited

cli_service_add stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_service_add": {
      "limits": [
        {
          "counter": "cli_service_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_service_add

What does the cli_service_add tool do? +

Install an optional service into a LaunchFrame project. Runs non-interactively (skips prompts). Env vars will be empty — configure them manually in infrastructure/.env afterward. It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cli_service_add? +

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

cli_service_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cli_service_add? +

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

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

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