Create a new Linear issue
AI agents use linear_create_issue to create or update resources in Curri MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Curri MCP Server environment.
Creating an issue is a reversible write operation—new issues can be updated or deleted later. It modifies the Linear system state by adding a new record, but does not destroy data or execute arbitrary code. The severity is medium because uncontrolled issue creation could spam a project tracking system or create misleading records, but the impact is contained and reversible.
From the tool's definition Tool name 'linear_create_issue' and description 'Create a new Linear issue' explicitly indicate the tool creates a new data record in the Linear issue tracking system.
Attacks that exploit this kind of access
Create a new Linear issue. It is categorised as a Write tool in the Curri MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Curri MCP 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 Curri MCP 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 Curri MCP Server MCP server (teamcurri/mcp-linear). 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 →