AI agents call linear_deleteCustomer 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.
This tool permanently removes a customer record from the Linear system. Deletion is an irreversible operation that destroys data and cannot be undone through normal means. While not as severe as 'critical' (which would require broad system compromise or cascading failures), the loss of a customer record represents significant data destruction.
From the tool's definition Tool name is 'linear_deleteCustomer' with description 'Delete a customer'. The verb 'delete' is explicitly destructive and irreversible.
Documented attack patterns abuse exactly the kind of access linear_deleteCustomer 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_deleteCustomer:
{
"version": "1",
"default": "deny",
"hide": [
"linear_deleteCustomer"
]
}linear_deleteCustomer 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 customer. 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_deleteCustomer: 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_deleteCustomer 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_deleteCustomer 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_deleteCustomer. 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_deleteCustomer 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.