Delete multiple tasks by IDs (permanent, cannot be undone).
AI agents call task_delete_bulk to permanently remove resources in Vector Task MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data in bulk without recovery option. While not financial in nature, the blast radius is high because an AI agent could accidentally or maliciously delete many tasks at once, destroying user work. The permanent nature and bulk deletion capability elevate it to Destructive rather than Write.
From the tool's definition Tool description explicitly states 'Delete multiple tasks by IDs (permanent, cannot be undone)' — the word 'permanent' and 'cannot be undone' are unambiguous markers of irreversible deletion.
Attacks that exploit this kind of access
Delete multiple tasks by IDs (permanent, cannot be undone). It is categorised as a Destructive tool in the Vector Task MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vector Task MCP Server MCP server in PolicyLayer and add a rule for task_delete_bulk: 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 Vector Task MCP Server. Nothing to install.
task_delete_bulk 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 task_delete_bulk 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 task_delete_bulk. 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.
task_delete_bulk is provided by the Vector Task MCP Server MCP server (xsaven/vector-task-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 →