cli_deploy_up · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_deploy_up does on LaunchFrame MCP

AI agents invoke cli_deploy_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_deploy_up needs a policy

This tool performs Execute-category actions: it runs external operations (SSH commands to a VPS) whose effects are substantial and depend on what images/services are deployed. While not irreversible in the destructive sense (deployments can be rolled back), it directly impacts production systems and could cause significant outages or service disruptions if misused.

From the tool's definition "Deploy the latest images to the VPS and restart all production services via SSH" — this tool executes remote operations (SSH commands) that trigger deployment and service restarts in production.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_deploy_up Rate-limited

cli_deploy_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_deploy_up": {
      "limits": [
        {
          "counter": "cli_deploy_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_deploy_up

What does the cli_deploy_up tool do? +

Deploy the latest images to the VPS and restart all production services via SSH. 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_deploy_up? +

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

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

Can I rate-limit cli_deploy_up? +

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

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

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