Critical Risk →

linear_deleteCustomerNeed

Delete a customer need

How to control linear_deleteCustomerNeed ↓

AI agents call linear_deleteCustomerNeed 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.

Critical Risk

The tool performs an irreversible deletion operation on a customer need record. Destructive actions are those that cannot be undone and permanently remove data. If an AI agent misuses this tool (e.g., deletes the wrong customer need due to confusion or a prompt injection), the data loss cannot be recovered through the tool itself.

From the tool's definition Tool name contains 'delete' and description states 'Delete a customer need' — this irreversibly removes data from the Linear system.

Documented attack patterns abuse exactly the kind of access linear_deleteCustomerNeed 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_deleteCustomerNeed:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "linear_deleteCustomerNeed"
  ]
}

linear_deleteCustomerNeed disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Linear — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the linear_deleteCustomerNeed tool do? +

Delete a customer need. 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.

How do I enforce a policy on linear_deleteCustomerNeed? +

Register the Linear MCP server in PolicyLayer and add a rule for linear_deleteCustomerNeed: 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.

What risk level is linear_deleteCustomerNeed? +

linear_deleteCustomerNeed is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit linear_deleteCustomerNeed? +

Yes. Add a rate_limit block to the linear_deleteCustomerNeed 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.

How do I block linear_deleteCustomerNeed completely? +

Set action: deny in the PolicyLayer policy for linear_deleteCustomerNeed. 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.

What MCP server provides linear_deleteCustomerNeed? +

linear_deleteCustomerNeed 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.

Enforce policy on every Linear tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.