Delete multiple tasks at once via V2 batch.
AI agents call batch_delete_tasks to permanently remove resources in Tick — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes tasks from the system without any indication of reversibility or undo capability. Deletion operations are irreversible by nature and fall squarely into the Destructive category. The batch nature increases the blast radius—an AI agent given insufficient constraints could delete many tasks simultaneously, causing significant data loss.
From the tool's definition Tool name contains 'delete' and description states 'Delete multiple tasks at once via V2 batch.' The word 'delete' combined with batch processing indicates irreversible removal of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete multiple tasks at once via V2 batch. It is categorised as a Destructive tool in the Tick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tick MCP server in PolicyLayer and add a rule for batch_delete_tasks: 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 Tick. Nothing to install.
batch_delete_tasks 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 batch_delete_tasks 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 batch_delete_tasks. 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.
batch_delete_tasks is provided by the Tick MCP server (kpihx/tick-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 →