This record as markdown: /tools/linear/linear-updateproject.md
What linear_updateProject does on Linear
AI agents use linear_updateProject 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 |
|---|---|---|---|
id | string | — | ID of the project to update |
name | string | — | New name of the project |
state | string | — | New state of the project (e.g., 'planned', 'started', 'paused', 'completed', 'canceled') |
content | string | — | New content of the project (Markdown supported) |
description | string | — | New short summary of the project |
Parameters from the server's own tool schema.
Why linear_updateProject is rated Medium
Updating a project is a reversible write operation that modifies data without deleting it. The severity is medium rather than high because project updates in a project management tool typically affect metadata, settings, or configurations rather than causing widespread data loss.
From the tool's definition Tool name is 'linear_updateProject' and description states 'Update an existing project in Linear' — the word 'Update' and verb form clearly indicates modification of existing data.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs linear_updateProject 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_updateProject, this is the rule to start with:
linear_updateProject 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_updateProject call is checked against it from then on.
Questions about linear_updateProject
Update an existing project in Linear. 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_updateProject accepts 5 parameters: id, name, state, content, description. 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_updateProject: 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_updateProject 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_updateProject 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_updateProject. 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_updateProject 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