Delete a ticket permanently.
AI agents call delete_ticket to permanently remove resources in Pearlog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Ticket ID to delete. |
Parameters from the server's own tool schema.
This tool permanently deletes tickets, which is an irreversible operation that cannot be undone. Destructive is the most severe applicable category. High severity reflects the risk that an AI agent could mistakenly or maliciously delete important project management records, affecting team collaboration and historical tracking. The action cannot be recovered through normal means.
From the tool's definition Tool name 'delete_ticket' combined with description 'Delete a ticket permanently' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a ticket permanently. It is categorised as a Destructive tool in the Pearlog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_ticket accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Pearlog 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 Pearlog. 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 Pearlog MCP server (mcp-server-pearlog). 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 →