This record as markdown: /tools/io-github-portel-dev-ncp/scale.md
What scale does on Ncp
AI agents invoke scale 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.
Why scale is rated High
Scaling EC2 resources is an executable action that modifies cloud infrastructure state. While not immediately destructive (instances can be scaled back down), it commits operational changes with cost and availability implications. This is more severe than Write (which is reversible data modification) because it triggers external infrastructure operations.
From the tool's definition Tool name 'scale' combined with description 'Scale aws-ec2-api resources' indicates triggering AWS EC2 scaling operations, which execute infrastructure changes with real-world effects (launching or terminating instances).
Attacks that exploit this kind of access
The rule that runs scale 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 scale, this is the rule to start with:
scale 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every scale call is checked against it from then on.
Questions about scale
Scale aws-ec2-api resources. 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.
Register the Ncp MCP server in PolicyLayer and add a rule for scale: 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.
scale is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scale 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.
Set action: deny in the PolicyLayer policy for scale. 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.
scale 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.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue