deploy_site

Deploy site to Netlify

SERVERNcp SOURCE@portel/ncp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/deploy-site.md

WHAT IT DOES

What deploy_site does on Ncp

AI agents invoke deploy_site to trigger actions in Ncp. 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.

RISK

Why deploy_site is rated High

This tool triggers an external operation (deployment of a site to Netlify) whose effects depend on which site/version is being deployed. Deployment is an irreversible action from the user's perspective (though technically revertible via another deployment), but primarily executes a build and publish process that affects production infrastructure.

From the tool's definition deploy_site: Deploy site to Netlify

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deploy_site safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deploy_site, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every deploy_site call is checked against it from then on.

FAQ

Questions about deploy_site

What does the deploy_site tool do? +

Deploy site to Netlify. It is categorised as a Execute tool in the Ncp 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 Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →