Move task to trash or delete permanently.
AI agents call delete_task to permanently remove resources in Streamline MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes user data. Even though it offers a 'move to trash' option as a softer alternative, the 'delete permanently' capability makes this Destructive rather than Write. The blast radius is high because an AI agent could permanently erase important tasks without recovery, causing data loss. Destructive is more severe than Execute or Write, so it takes precedence.
From the tool's definition Tool name is 'delete_task' and description explicitly states 'delete permanently', which irreversibly removes data. The capability to permanently delete tasks (not just archive or mark complete) means the action cannot be undone.
Attacks that exploit this kind of access
Move task to trash or delete permanently. It is categorised as a Destructive tool in the Streamline MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Streamline 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 Streamline MCP. 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 Streamline MCP server (rostehea/streamline-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 →