DELETE a task permanently.
AI agents call delete_task to permanently remove resources in Nexus Core — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a task without the ability to undo the action. This is a destructive operation that eliminates data irreversibly. While the blast radius is somewhat contained to individual task records rather than system-wide data, the permanent nature and lack of recovery mechanism warrants 'high' severity in a personal assistant context where tasks may contain important reminders or records.
From the tool's definition Tool name 'delete_task' combined with description 'DELETE a task permanently' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
DELETE a task permanently. It is categorised as a Destructive tool in the Nexus Core MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nexus Core MCP server in PolicyLayer and add a rule for delete_task: 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 Nexus Core. Nothing to install.
delete_task 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_task 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_task. 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_task is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →