linear_removeProjectFromInitiative
Remove a project from an initiative
This record as markdown: /tools/linear/linear-removeprojectfrominitiative.md
What linear_removeProjectFromInitiative does on Linear
AI agents use linear_removeProjectFromInitiative to create or update resources in Linear, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectId | string | — | The ID of the project to remove |
initiativeId | string | — | The ID of the initiative |
Parameters from the server's own tool schema.
Why linear_removeProjectFromInitiative is rated Medium
Removing a project from an initiative modifies an association/relationship between entities in Linear. This is a reversible write operation (the project can be re-added), not a deletion of the project or initiative itself. Misuse could disrupt project organization but is recoverable.
From the tool's definition Remove a project from an initiative
Attacks that exploit this kind of access
The rule that runs linear_removeProjectFromInitiative 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_removeProjectFromInitiative, this is the rule to start with:
linear_removeProjectFromInitiative stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every linear_removeProjectFromInitiative call is checked against it from then on.
Questions about linear_removeProjectFromInitiative
Remove a project from an initiative. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
linear_removeProjectFromInitiative accepts 2 parameters: projectId, 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_removeProjectFromInitiative: 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_removeProjectFromInitiative is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the linear_removeProjectFromInitiative 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_removeProjectFromInitiative. 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_removeProjectFromInitiative 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.
This server
Across the catalogue