AI agents use linear_link_issues to create or update resources in Linearapp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linearapp environment.
Creating relationships between issues is a reversible modification operation that alters metadata/structure but does not delete data or execute arbitrary code. This falls under Write category. Severity is medium because unauthorized linking could confuse issue tracking and project management, but the effect is bounded to relationship metadata and easily correctable.
From the tool's definition Tool name 'linear_link_issues' and description 'Create a relationship between issues in Linear' indicate the tool modifies issue state by establishing or changing relationships between issues.
Attacks that exploit this kind of access
Create a relationship between issues in Linear. It is categorised as a Write tool in the Linearapp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linearapp MCP server in PolicyLayer and add a rule for linear_link_issues: 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 Linearapp. Nothing to install.
linear_link_issues 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_link_issues 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_link_issues. 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_link_issues is provided by the Linearapp MCP server (mcp-server-linearapp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →