Delete a Linear issue
AI agents call linear_delete_issue to permanently remove resources in Curri MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an issue from Linear's system. Deletion is an irreversible operation with no undo mechanism—the data cannot be recovered. This fits the Destructive category definition of 'irreversibly deletes or overwrites data'. While the blast radius for a single issue deletion may be moderate, the inability to undo makes this high severity.
From the tool's definition Tool name: 'linear_delete_issue'. Description: 'Delete a Linear issue'. The word 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a Linear issue. It is categorised as a Destructive tool in the Curri MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Curri MCP Server MCP server in PolicyLayer and add a rule for linear_delete_issue: 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 Curri MCP Server. Nothing to install.
linear_delete_issue 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 linear_delete_issue 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 linear_delete_issue. 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.
linear_delete_issue is provided by the Curri MCP Server MCP server (teamcurri/mcp-linear). 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 →