linear_update_issue_status · Integrations MCP: Risk & Policy

WHAT IT DOES

What linear_update_issue_status does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why linear_update_issue_status needs a policy

This tool modifies existing data (issue status) in a reversible manner — statuses can be changed back or updated again. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or trigger external operations with unpredictable side effects beyond the scope of Linear.

From the tool's definition Tool name 'linear_update_issue_status' explicitly indicates modification of issue status in Linear (a project management platform). The 'update' verb confirms it performs a write operation rather than a read-only action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_update_issue_status Rate-limited

linear_update_issue_status 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_status": {
      "limits": [
        {
          "counter": "linear_update_issue_status_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about linear_update_issue_status

What does the linear_update_issue_status tool do? +

linear_update_issue_status. It is categorised as a Write tool in the Integrations 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_status? +

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

What risk level is linear_update_issue_status? +

linear_update_issue_status 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_status? +

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

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

linear_update_issue_status is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.