This record as markdown: /tools/io-github-portel-dev-ncp/bulk-delete.md
What bulk_delete does on Ncp
AI agents call bulk_delete 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 bulk_delete is rated Critical
Bulk deletion operations are inherently destructive as they irreversibly remove data at scale. This poses a high risk if an AI agent misuses the tool with incorrect selection criteria, resulting in unintended permanent loss of multiple documents. The blast radius is significant due to the bulk nature of the operation.
From the tool's definition Tool name 'bulk_delete' combined with description 'Bulk delete documents' explicitly indicates irreversible deletion of multiple records. The 'delete' operation and 'bulk' scope demonstrate data destruction that cannot be undone.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_delete 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 bulk_delete, this is the rule to start with:
bulk_delete 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 bulk_delete call is checked against it from then on.
Questions about bulk_delete
Bulk delete documents. 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 bulk_delete: 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.
bulk_delete 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 bulk_delete 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 bulk_delete. 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.
bulk_delete 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