Delete a task from the task list. Use this to clean up old completed tasks.
AI agents call delete-task to permanently remove resources in Back-Agent MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (task records) and the action cannot be undone. While the blast radius is limited to task metadata rather than code or external systems, deletion is inherently destructive. The context of a development task automation system means deleted tasks could include important historical records of work performed.
From the tool's definition Tool name contains 'delete' and description states 'Delete a task from the task list.' The action is irreversible—once deleted, the task record cannot be recovered.
Attacks that exploit this kind of access
Delete a task from the task list. Use this to clean up old completed tasks. It is categorised as a Destructive tool in the Back-Agent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Back-Agent MCP Server 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 Back-Agent MCP Server. 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 Back-Agent MCP Server MCP server (zuens2020/back-agent-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 →