This record as markdown: /tools/io-github-portel-dev-ncp/remove.md
What remove does on Ncp
AI agents call remove to permanently remove resources in Ncp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove is rated Critical
The tool removes MCP servers from the orchestration configuration. While the word 'remove' could theoretically be reversible, removing a server from an N-to-1 orchestration gateway's configuration is a destructive action that eliminates routing, tool discovery, and integration for that server.
From the tool's definition Tool name 'remove' combined with description 'Remove an MCP server from NCP configuration' indicates irreversible deletion of configuration state. This alters the system's persistent configuration in a way that cannot be automatically undone.
Attacks that exploit this kind of access
The rule that runs remove 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 remove, this is the rule to start with:
remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every remove call is checked against it from then on.
Questions about remove
Remove an MCP server from NCP configuration. First use. It is categorised as a Destructive tool in the Ncp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ncp MCP server in PolicyLayer and add a rule for remove: 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.
remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove 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 remove. 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.
remove 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.
Across the catalogue