update_issue

Update an existing issue

SERVERLinear Kanban Server SOURCE0xikarus/linear-kanban-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xikarus-linear-kanban-mcp/update-issue.md

WHAT IT DOES

What update_issue does on Linear Kanban Server

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

RISK

Why update_issue is rated Medium

This tool creates or modifies data in a reversible manner—the defining characteristic of the Write category. Updates to issues can typically be undone or corrected (e.g., changing status, assignee, description), distinguishing it from Destructive actions.

From the tool's definition Tool named 'update_issue' with description 'Update an existing issue' clearly modifies existing data. The Linear server description confirms it 'enables management of Linear kanban boards, projects, and issues directly.' Sibling tools include destructive…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_issue safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linear Kanban Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_issue, this is the rule to start with:

update_issue Rate-limited

update_issue 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": {
    "update_issue": {
      "limits": [
        {
          "counter": "update_issue_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 Kanban Server, apply this rule, and every update_issue call is checked against it from then on.

FAQ

Questions about update_issue

What does the update_issue tool do? +

Update an existing issue. It is categorised as a Write tool in the Linear Kanban 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 update_issue? +

Register the Linear Kanban Server MCP server in PolicyLayer and add a rule for update_issue: 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 Kanban Server. Nothing to install.

What risk level is update_issue? +

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

Can I rate-limit update_issue? +

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

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

update_issue is provided by the Linear Kanban Server MCP server (0xikarus/linear-kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linear Kanban Server, and thousands of servers like it.

This server

All 22 Linear Kanban Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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