Delete a ranking pipeline.
AI agents call delete_pipeline 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 permanently removes a ranking pipeline, which cannot be undone. Deletion operations are categorized as Destructive rather than Write because they irreversibly destroy data. The severity is high because accidental deletion of a pipeline could disrupt recommendation engine operations and affect all dependent workflows (e.g., campaigns using that pipeline).
From the tool's definition Tool name 'delete_pipeline' with description 'Delete a ranking pipeline' - the verb 'delete' explicitly indicates irreversible removal of data/configuration.
Attacks that exploit this kind of access
Delete a ranking pipeline. 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_pipeline: 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_pipeline 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_pipeline 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_pipeline. 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_pipeline 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 →