linear_updateIssue · Linear MCP Server MCP: Risk & Policy

WHAT IT DOES

What linear_updateIssue does on Linear MCP Server

AI agents use linear_updateIssue to create or update resources in Linear MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Server environment.

WHY IT NEEDS A POLICY

Why linear_updateIssue needs a policy

The tool creates or modifies data reversibly by updating an existing issue. While this affects project state and team visibility, the operation is reversible (updates can be undone by subsequent updates), and does not involve financial impact, code execution, or irreversible deletion. This fits the Write category.

From the tool's definition Tool name is 'linear_updateIssue' and description states 'Update an existing issue in Linear' — this directly modifies existing data in a project management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linear MCP Server, so you can run agents against it safely.

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 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on linear_updateIssue? +

Register the Linear MCP Server 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 MCP Server. 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 MCP server (wkoutre/linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.