Delete an existing comment in Linear
AI agents call delete_comment to permanently remove resources in Linear — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of comments is an irreversible, destructive operation that cannot be undone. While the blast radius is somewhat limited to individual comment removal rather than bulk data loss, it still permanently removes user-generated content. Severity is 'high' rather than 'critical' because the impact is scoped to a single comment rather than a cascading destructive operation across issues or projects.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete an existing comment in Linear' — this irreversibly removes data.
Attacks that exploit this kind of access
Delete an existing comment in Linear. It is categorised as a Destructive tool in the Linear MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linear MCP server in PolicyLayer and add a rule for delete_comment: 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. Nothing to install.
delete_comment 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_comment 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_comment. 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_comment is provided by the Linear MCP server (mkusaka/mcp-server-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 →