Delete a ticket in Freshservice.
AI agents call delete_ticket to permanently remove resources in Freshservice MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a ticket cannot be undone and results in permanent loss of incident/request records, associated communications, and audit trails. This is a destructive operation that removes data irreversibly. While not financial in nature, the high severity reflects the potential business impact of losing critical service management records and the inability to recover them.
From the tool's definition Tool named 'delete_ticket' with description 'Delete a ticket in Freshservice' — the verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a ticket in Freshservice. It is categorised as a Destructive tool in the Freshservice MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshservice MCP Server 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 Freshservice MCP Server. 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 Freshservice MCP Server MCP server (leemangold/freshservice_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 →