AI agents call delete-issue-relation 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 that cannot be undone are categorized as Destructive, the second-most severe category. While the blast radius is somewhat contained (deleting a relation rather than an entire issue), the operation is irreversible. Removing issue relationships could break project tracking, audit trails, or workflow dependencies, warranting 'high' severity.
From the tool's definition Tool name is 'delete-issue-relation' which explicitly performs a deletion operation. The verb 'delete' indicates irreversible removal of data (a relationship between issues). No description provided, but the name clearly indicates destructive intent.
Documented attack patterns abuse exactly the kind of access delete-issue-relation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linear MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-issue-relation:
{
"version": "1",
"default": "deny",
"hide": [
"delete-issue-relation"
]
}delete-issue-relation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete-issue-relation. 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 delete-issue-relation: 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.
delete-issue-relation 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-issue-relation 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-issue-relation. 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-issue-relation is provided by the Linear MCP Server MCP server (samcfinan/linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linear MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Linear MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.