Delete multiple tickets in a single batch operation. Best-effort: all items attempted, per-item results reported. Requires TICKET_ADMIN permission.
AI agents call ticket_batch_delete to permanently remove resources in Trac — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion is a destructive operation that cannot be undone. The batch nature multiplies the blast radius—a single misuse could destroy many tickets at once. Requires TICKET_ADMIN permission, but once invoked, the damage is irreversible. This is more severe than Execute (which might trigger reversible operations) and far more severe than Write (which modifies data reversibly).
From the tool's definition Tool name: ticket_batch_delete. Description: "Delete multiple tickets in a single batch operation." The term "delete" combined with "batch" indicates irreversible removal of potentially many data records at once.
Attacks that exploit this kind of access
Delete multiple tickets in a single batch operation. Best-effort: all items attempted, per-item results reported. Requires TICKET_ADMIN permission. It is categorised as a Destructive tool in the Trac MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trac MCP server in PolicyLayer and add a rule for ticket_batch_delete: 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 Trac. Nothing to install.
ticket_batch_delete 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 ticket_batch_delete 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 ticket_batch_delete. 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.
ticket_batch_delete is provided by the Trac MCP server (nerpatech/trac-mcp-server). 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 →