linear_create_issue
AI agents use linear_create_issue to create or update resources in Linear MCP Integration Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Integration Server environment.
Creating issues is a reversible write operation that modifies the Linear database by adding new records. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because creating spam or malicious issues could disrupt project management workflows, but the impact is limited in scope and reversible (issues can be deleted).
From the tool's definition Tool name 'linear_create_issue' combined with server description stating it supports 'creating issues' indicates this tool creates new data in Linear's issue tracking system.
Attacks that exploit this kind of access
linear_create_issue. It is categorised as a Write tool in the Linear MCP Integration Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linear MCP Integration Server MCP server in PolicyLayer and add a rule for linear_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 Linear MCP Integration Server. Nothing to install.
linear_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 linear_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 linear_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.
linear_create_issue is provided by the Linear MCP Integration Server MCP server (skspade/mcp-linear-server). 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 →