Delete a ticket by display number
AI agents call delete_ticket to permanently remove resources in Tickr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
number | string | Yes | Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed) |
Parameters from the server's own tool schema.
Deletion of a ticket is an irreversible operation that removes data and cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' In a project management context, deleting a ticket loses associated information, comments, history, and relationships.
From the tool's definition Tool name 'delete_ticket' explicitly indicates deletion. Description states 'Delete a ticket by display number' — uses the verb 'Delete' which is irreversible.
Attacks that exploit this kind of access
Delete a ticket by display number. It is categorised as a Destructive tool in the Tickr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_ticket accepts 1 parameter: number. Required: number. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for delete_ticket: 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 Tickr. Nothing to install.
delete_ticket 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_ticket 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_ticket. 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_ticket is provided by the Tickr MCP server (@k-system/tickr-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 →