linear_update_issue · Integrations MCP: Risk & Policy

WHAT IT DOES

What linear_update_issue does on Integrations MCP

AI agents use linear_update_issue 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 needs a policy

The tool modifies existing issue records in Linear. While the description is empty (lowering confidence slightly), the function name clearly indicates a reversible data modification rather than creation, deletion, or execution. This is a Write-category risk.

From the tool's definition Tool name 'linear_update_issue' indicates modification of issue data in Linear (a project management platform). The verb 'update' is characteristic of Write operations that create or modify data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

What does the linear_update_issue tool do? +

linear_update_issue. 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? +

Register the Integrations 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 Integrations 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 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.