deploy · Run402 MCP: Risk & Policy

WHAT IT DOES

What deploy does on Run402

AI agents invoke deploy to trigger actions in Run402. 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 deploy needs a policy

This tool executes infrastructure-level operations that trigger external effects: database migrations run, functions deploy, web routes are modified, and subdomains are configured. These are code/configuration execution actions whose effects depend on the ReleaseSpec arguments provided. While it doesn't permanently delete data, it modifies live infrastructure and can affect service availability.

From the tool's definition Tool accepts ReleaseSpec with database migrations, function deployments, site configuration, routes, and subdomains.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy Rate-limited

deploy 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": {
    "deploy": {
      "limits": [
        {
          "counter": "deploy_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 Run402, so you can run agents against it safely.

FAQ

Questions about deploy

What does the deploy tool do? +

Unified apply primitive. Accepts a structured ReleaseSpec — database (migrations + expose), value-free secrets.require/delete declarations, functions, site, site.public_paths, subdomains, and routes.replace web routes — with explicit replace vs patch semantics per resource. Use site.public_paths for clean static URLs such as /events backed by release asset events.html; explicit mode does not expose /events.html unless separately declared, while mode:. It is categorised as a Execute tool in the Run402 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy? +

Register the Run402 MCP server in PolicyLayer and add a rule for deploy: 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 Run402. Nothing to install.

What risk level is deploy? +

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

Can I rate-limit deploy? +

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

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

deploy is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.