deploy

Deploy using aws-ec2-api

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

WHAT IT DOES

What deploy does on Ncp

AI agents invoke deploy 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 is rated High

Deploying to EC2 is an Execute action that triggers external infrastructure changes whose effects depend on the deployment arguments (what code/configuration is deployed, to which instances, in what region). The blast radius is high as it can affect production systems, but not Financial or Destructive (assuming deployments are reversible through rollback or replacement).

From the tool's definition Tool name 'deploy' combined with description 'Deploy using aws-ec2-api' indicates execution of deployment operations against AWS EC2 infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deploy 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, this is the rule to start with:

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.

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

FAQ

Questions about deploy

What does the deploy tool do? +

Deploy using aws-ec2-api. 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? +

Register the Ncp 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 Ncp. 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 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 →