linear_subscribeToIssue · Linear MCP Server MCP

WHAT IT DOES

What linear_subscribeToIssue does on Linear MCP Server

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

Subscribing to an issue is a Write operation because it creates or modifies subscription metadata in the system. While it lacks destructive effects (not Destructive) or financial impact, it does change application state. The severity is medium because an AI misusing this tool could spam subscriptions or modify notification settings at scale, but the impact is reversible and non-critical to core data integrity.

From the tool's definition Subscribing to an issue involves modifying user notification preferences or subscription state in Linear. The description 'Subscribe to issue updates' indicates a state change operation that creates or modifies the user's relationship to an issue (adding them…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_subscribeToIssue Rate-limited

linear_subscribeToIssue 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_subscribeToIssue": {
      "limits": [
        {
          "counter": "linear_subscribetoissue_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_subscribeToIssue

What does the linear_subscribeToIssue tool do? +

Subscribe to issue updates. 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_subscribeToIssue? +

Register the Linear MCP Server MCP server in PolicyLayer and add a rule for linear_subscribeToIssue: 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_subscribeToIssue? +

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

Can I rate-limit linear_subscribeToIssue? +

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

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

linear_subscribeToIssue 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.