Delete a user segment. Any rules referencing this segment will need to be updated.
AI agents call delete_segment 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 data (a user segment) from the system. Deletion is irreversible and could disrupt dependent business logic (rules referencing the segment). While not directly financial, the blast radius is significant—misconfigured deletion could break targeting logic, affect user experiences, or require manual remediation.
From the tool's definition Tool name is 'delete_segment' with description stating it will 'Delete a user segment.' The verb 'delete' combined with the explicit action of removing a segment is irreversible.
Attacks that exploit this kind of access
Delete a user segment. Any rules referencing this segment will need to be updated. 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_segment: 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_segment 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_segment 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_segment. 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_segment 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 →