linear_update_issue

Update an existing Linear issue

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/linear-update-issue.md

WHAT IT DOES

What linear_update_issue does on Sage MCP

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

RISK

Why linear_update_issue is rated Medium

This tool modifies existing issue data in Linear (a project management system) but does not delete data irreversibly. Updates are reversible—prior versions can typically be recovered or the issue can be reverted to a previous state.

From the tool's definition Tool name 'linear_update_issue' combined with description 'Update an existing Linear issue' indicates modification of data. The verb 'update' is explicitly stated as a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_update_issue safely

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

linear_update_issue Rate-limited

linear_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": {
    "linear_update_issue": {
      "limits": [
        {
          "counter": "linear_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 Sage MCP, apply this rule, and every linear_update_issue call is checked against it from then on.

FAQ

Questions about linear_update_issue

What does the linear_update_issue tool do? +

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

Register the Sage MCP server in PolicyLayer and add a rule for linear_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 Sage MCP. Nothing to install.

What risk level is linear_update_issue? +

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

Can I rate-limit linear_update_issue? +

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

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

linear_update_issue is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage 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 →