This record as markdown: /tools/instantkom-mcp-server/delete-ticket.md
What delete_ticket does on instantKOM MCP Server
AI agents call delete_ticket to permanently remove resources in instantKOM MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_ticket is rated Critical
The tool performs an irreversible delete operation on ticket records. Deletion cannot be undone and results in permanent data loss. This meets the definition of Destructive category. Severity is high because unintended deletion of tickets could disrupt customer support workflows and lose important communication history, though it is scoped to individual tickets rather than bulk operations (which would be critical).
From the tool's definition Tool name 'delete_ticket' with description 'Delete a ticket by ID' indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_ticket safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_ticket, this is the rule to start with:
delete_ticket is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every delete_ticket call is checked against it from then on.
Questions about delete_ticket
Delete a ticket by ID. It is categorised as a Destructive tool in the instantKOM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the instantKOM 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 instantKOM 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 instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
Across the catalogue