This record as markdown: /tools/linear/linear-deleteinitiative.md
What linear_deleteInitiative does on Linear
AI agents call linear_deleteInitiative 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
initiativeId | string | — | The ID of the initiative to delete |
Parameters from the server's own tool schema.
Why linear_deleteInitiative is rated Critical
The tool permanently removes an initiative from the system by moving it to trash. This is a destructive action that cannot be undone through normal means and could result in loss of project planning data, especially if the initiative contains multiple issues or team commitments. In a Linear workspace context, deleting initiatives could disrupt project organization and team coordination.
From the tool's definition Tool name contains 'delete' and description states 'Delete an initiative (move to trash)' - this is an irreversible removal operation.
Attacks that exploit this kind of access
The rule that runs linear_deleteInitiative safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_deleteInitiative, this is the rule to start with:
linear_deleteInitiative is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every linear_deleteInitiative call is checked against it from then on.
Questions about linear_deleteInitiative
Delete an initiative (move to trash). 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.
linear_deleteInitiative accepts 1 parameter: initiativeId. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for linear_deleteInitiative: 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_deleteInitiative 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_deleteInitiative 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_deleteInitiative. 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_deleteInitiative is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
Across the catalogue