Delete a ticket permanently. Warning: This cannot be undone. Requires TICKET_ADMIN permission and
AI agents call ticket_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.
This tool irreversibly deletes data (tickets) from the Trac project management system. Permanent deletion without undo is the defining characteristic of the Destructive category. While the blast radius is somewhat limited to individual tickets rather than system-wide data, the permanence and irreversibility elevate it above Write or Execute.
From the tool's definition 'Delete a ticket permanently. Warning: This cannot be undone.' — the tool explicitly states permanent deletion with no undo capability.
Attacks that exploit this kind of access
Delete a ticket permanently. Warning: This cannot be undone. Requires TICKET_ADMIN permission and. 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_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_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_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_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_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 →