Delete multiple issues
AI agents call linear_delete_issues to permanently remove resources in Linear MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and cannot be undone. Deleting multiple issues in bulk amplifies the blast radius—an AI agent with a mistaken instruction or prompt injection could permanently destroy substantial work tracking data, project history, and associated metadata. This meets the Destructive category definition of 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Tool name is 'linear_delete_issues' and description states 'Delete multiple issues'. The verb 'delete' combined with 'multiple' indicates irreversible removal of data at scale.
Attacks that exploit this kind of access
Delete multiple issues. It is categorised as a Destructive tool in the Linear MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for linear_delete_issues: 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 Linear MCP Server. Nothing to install.
linear_delete_issues 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_issues 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_issues. 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_issues is provided by the Linear MCP Server MCP server (timottowitz/linear-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 →