deploy_site · Ploi MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_site does on Ploi MCP Server

AI agents invoke deploy_site to trigger actions in Ploi MCP Server. 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 pipeline, which is a complex operation triggering external infrastructure changes. While not directly destructive (no data deletion), it modifies live production systems and could introduce breaking changes, outages, or data corruption depending on deployment content. The blast radius spans infrastructure state, making it Execute rather than Write.

From the tool's definition Tool description states 'Trigger deployment for a site and wait for it to complete' — the verb 'trigger' and 'deployment' indicate execution of external operations (build/release pipeline) whose effects depend on what code is being deployed.

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 Ploi MCP Server, so you can run agents against it safely.

FAQ

Questions about deploy_site

What does the deploy_site tool do? +

Trigger deployment for a site and wait for it to complete. Returns status when done. It is categorised as a Execute tool in the Ploi MCP Server 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 Ploi MCP Server 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 Ploi MCP Server. 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 Ploi MCP Server MCP server (sudanese/ploi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.