Permanently remove one or more items from the recommendation catalogue.
AI agents call delete_items to permanently remove resources in NeuronSearchLab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (catalogue items) and cannot be undone. Destructive operations are more severe than Write operations because they eliminate information permanently. In the context of a recommendation engine's catalogue, deletion affects system functionality and data integrity.
From the tool's definition Tool description explicitly states 'Permanently remove one or more items from the recommendation catalogue' — the verb 'permanently remove' combined with the irreversible nature of deletion from a catalogue indicates data destruction.
Attacks that exploit this kind of access
Permanently remove one or more items from the recommendation catalogue. It is categorised as a Destructive tool in the NeuronSearchLab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for delete_items: 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 NeuronSearchLab. Nothing to install.
delete_items 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 delete_items 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 delete_items. 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.
delete_items is provided by the NeuronSearchLab MCP server (neuronsearchlab/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →