This record as markdown: /tools/linear/linear-updateinitiative.md
What linear_updateInitiative does on Linear
AI agents use linear_updateInitiative 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 |
|---|---|---|---|
icon | string | — | Updated icon emoji |
name | string | — | Updated name of the initiative |
color | string | — | Updated color in hex format |
status | string | — | Updated status of the initiative |
content | string | — | Updated content in markdown format |
ownerId | string | — | Updated owner ID |
targetDate | string | — | Updated target completion date (ISO 8601 format) |
description | string | — | Updated description of the initiative |
initiativeId | string | — | The ID of the initiative to update |
Parameters from the server's own tool schema.
Why linear_updateInitiative is rated Medium
This tool modifies existing initiative records in Linear, a project management system. Updates are reversible and do not permanently delete data, so it is categorized as Write rather than Destructive.
From the tool's definition Tool name 'linear_updateInitiative' and description 'Update an existing initiative' indicate modification of existing data.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs linear_updateInitiative 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_updateInitiative, this is the rule to start with:
linear_updateInitiative 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_updateInitiative call is checked against it from then on.
Questions about linear_updateInitiative
Update an existing 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_updateInitiative accepts 9 parameters: icon, name, color, status, content, ownerId, targetDate, description, 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_updateInitiative: 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_updateInitiative 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_updateInitiative 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_updateInitiative. 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_updateInitiative 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