linear_updateIssue

Update an existing issue in Linear

SERVERLinear SOURCE@linear-mcp-server

Medium RISK CLASS

Category Write

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/linear/linear-updateissue.md

WHAT IT DOES

What linear_updateIssue does on Linear

AI agents use linear_updateIssue 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 or identifier of the issue to update (e.g., ABC-123)
`title`	string	—	New title for the issue
`teamId`	string	—	ID of the team to move the issue to
`cycleId`	string	—	ID of the cycle to move the issue to, or null to remove from current cycle
`dueDate`	string	—	The new due date for the issue (YYYY-MM-DD format), or null to remove
`stateId`	string	—	ID of the new state for the issue
`estimate`	number	—	The estimated complexity/points for the issue
`labelIds`	array	—	IDs of the labels to set on the issue (replacing existing labels)
`parentId`	string	—	ID of the parent issue, or null to convert to a regular issue
`priority`	number	—	New priority for the issue (0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low)
`projectId`	string	—	ID of the project to move the issue to
`sortOrder`	number	—	The position of the issue in relation to other issues

Parameters from the server's own tool schema.

RISK

Why linear_updateIssue is rated Medium

This tool modifies existing issue records in Linear, which is a reversible write operation. While it changes data, updates are not destructive (data is not deleted) and can typically be undone. The severity is medium because misuse could modify important project tracking data, affecting team workflows, but the impact is recoverable.

From the tool's definition Tool name 'updateIssue' and description 'Update an existing issue in Linear' indicate modification of existing data.

Risk signalsHigh parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_updateIssue 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_updateIssue, this is the rule to start with:

linear_updateIssue Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_updateIssue": {
      "limits": [
        {
          "counter": "linear_updateissue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every linear_updateIssue call is checked against it from then on.

FAQ

Questions about linear_updateIssue

What does the linear_updateIssue tool do? +

Update an existing issue 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.

What parameters does linear_updateIssue accept? +

linear_updateIssue accepts 12 parameters: id, title, teamId, cycleId, dueDate, stateId, estimate, labelIds, parentId, priority, projectId, sortOrder. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on linear_updateIssue? +

Register the Linear MCP server in PolicyLayer and add a rule for linear_updateIssue: 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_updateIssue? +

linear_updateIssue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit linear_updateIssue? +

Yes. Add a rate_limit block to the linear_updateIssue 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_updateIssue completely? +

Set action: deny in the PolicyLayer policy for linear_updateIssue. 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_updateIssue? +

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

KEEP EXPLORING

More on Linear, and thousands of servers like it.

This server

All 66 Linear tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →