AI agents call linear_deleteComment 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.
Deleting a comment is a destructive action that cannot be undone. Once deleted, the comment is permanently removed from the Linear issue/project and cannot be recovered through normal means. While the blast radius is limited to a single comment (not a critical business object like an entire project or financial record), it represents an irreversible data loss operation, placing it in the Destructive category.
From the tool's definition Tool name is 'linear_deleteComment' and description states 'Delete a comment' — the verb 'Delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access linear_deleteComment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linear, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_deleteComment:
{
"version": "1",
"default": "deny",
"hide": [
"linear_deleteComment"
]
} linear_deleteComment 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 a comment. 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 linear_deleteComment: 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.
linear_deleteComment 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_deleteComment 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_deleteComment. 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_deleteComment is provided by the Linear MCP server (tacticlaunch/mcp-linear). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 182 Linear tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
182 Linear tools catalogued and risk-classified — across an index of 42,500+ MCP servers.