Delete a recommendation context. This also removes associated pipelines and rules.
AI agents call delete_context 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 performs irreversible deletion of data (contexts, pipelines, and rules). It cannot be undone and has a cascading effect on related entities. While not financial or requiring shell execution, the destructive nature of permanently removing recommendation contexts and their dependent objects makes this a Destructive category risk with high severity due to the potential business impact of losing recommendation…
From the tool's definition Tool name is 'delete_context' and description states 'Delete a recommendation context. This also removes associated pipelines and rules.' The use of 'Delete' combined with cascading deletion of associated data ('also removes associated pipelines and rules')…
Attacks that exploit this kind of access
Delete a recommendation context. This also removes associated pipelines and rules. 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_context: 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_context 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_context 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_context. 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_context 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 →