deploy_site · Run402 MCP: Risk & Policy

WHAT IT DOES

What deploy_site does on Run402

AI agents invoke deploy_site 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_site needs a policy

This tool executes a deployment operation which runs code/scripts on external infrastructure (staging files, uploading to a gateway). While it's limited to static site deployment (not arbitrary code execution), it still triggers external operations whose effects depend on the supplied file arguments and could impact live infrastructure.

From the tool's definition Tool deploys a static site by staging files to a temp directory and uploading via transport mechanism. The description mentions 'Files are staged to a temp directory, then uploaded' and references a 'v1.32 plan/commit transport', indicating execution of a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_site Rate-limited

deploy_site 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_site": {
      "limits": [
        {
          "counter": "deploy_site_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_site

What does the deploy_site tool do? +

Deploy a static site (HTML/CSS/JS) from inline file bytes. Files are staged to a temp directory, then uploaded via the v1.32 plan/commit transport — only bytes the gateway doesn. 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_site? +

Register the Run402 MCP server in PolicyLayer and add a rule for deploy_site: 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_site? +

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

Can I rate-limit deploy_site? +

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

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

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