cli_waitlist_up · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_waitlist_up does on LaunchFrame MCP

AI agents invoke cli_waitlist_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_waitlist_up needs a policy

This tool executes an external operation (Docker container startup) that has observable side effects on the local system. While not destructive or financial, it modifies system state by launching services. An agent misusing this could start unwanted services, consume resources, or interfere with other running processes. The 'Start' verb and Docker Compose invocation confirm Execute category rather than Read or Write.

From the tool's definition Tool performs 'Start the waitlist service locally using Docker Compose' – actively runs/triggers Docker Compose to spawn a service, which are external operations with effects dependent on system state and configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_waitlist_up Rate-limited

cli_waitlist_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_waitlist_up": {
      "limits": [
        {
          "counter": "cli_waitlist_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_waitlist_up

What does the cli_waitlist_up tool do? +

Start the waitlist service locally using Docker Compose. 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_waitlist_up? +

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

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

Can I rate-limit cli_waitlist_up? +

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

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

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