This record as markdown: /tools/linear/linear-subscribetoissue.md
What linear_subscribeToIssue does on Linear
AI agents use linear_subscribeToIssue to create or update resources in Linear, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
issueId | string | — | ID or identifier of the issue to subscribe to (e.g., ABC-123) |
Parameters from the server's own tool schema.
Why linear_subscribeToIssue is rated Medium
Subscribing to an issue updates the user's notification preferences for that issue—a state change that is reversible (can unsubscribe). This is a write operation rather than read-only or destructive. The blast radius is minimal since it only affects the user's own subscription state and doesn't modify core issue data or have financial implications.
From the tool's definition Tool name 'subscribeToIssue' and description 'Subscribe to issue updates' indicates modifying subscription state for an issue, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs linear_subscribeToIssue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_subscribeToIssue, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every linear_subscribeToIssue call is checked against it from then on.
Questions about linear_subscribeToIssue
Subscribe to issue updates. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
linear_subscribeToIssue accepts 1 parameter: issueId. The full parameter table on this page comes from the server's own tool schema.
Register the Linear 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. Nothing to install.
linear_subscribeToIssue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
linear_subscribeToIssue is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue