This record as markdown: /tools/io-github-portel-dev-ncp/add-step.md
What add_step does on Ncp
AI agents use add_step to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why add_step is rated Medium
This tool creates or modifies workflow/process data by adding steps, which is a reversible operation typical of Write category. It does not delete data (Destructive), move money (Financial), execute arbitrary code (Execute), or simply retrieve data (Read). Severity is medium because misuse could corrupt a thinking/planning process, but the impact is limited to that workflow.
From the tool's definition Tool name 'add_step' and description 'Add a step to the thinking process' indicate creation/modification of process workflow data. The action is reversible (steps can be removed or edited).
Attacks that exploit this kind of access
The rule that runs add_step 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 add_step, this is the rule to start with:
add_step stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 add_step call is checked against it from then on.
Questions about add_step
Add a step to the thinking process. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for add_step: 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.
add_step is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_step 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 add_step. 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.
add_step 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