A tool that creates an issue in Linear
AI agents use create_issue to create or update resources in MCP Linear App — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Linear App environment.
Creating an issue in a project management system is a Write operation—it generates new data that can be modified or deleted later. The severity is medium because misuse could create spam issues, clutter the project workspace, or pollute the audit trail, but the effects are reversible. The confidence is high given explicit language about issue creation.
From the tool's definition Tool name 'create_issue' and description 'creates an issue in Linear' indicate data creation. Server description confirms it supports 'creating...issues' as a reversible operation.
Attacks that exploit this kind of access
A tool that creates an issue in Linear. It is categorised as a Write tool in the MCP Linear App MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Linear App MCP server in PolicyLayer and add a rule for create_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 MCP Linear App. Nothing to install.
create_issue 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_issue is provided by the MCP Linear App MCP server (zalab-inc/mcp-linear-app). 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 →