linear_create_issue
Create a new issue in Linear with title and optional description. Returns issue ID, key, title, and URL.
This record as markdown: /tools/io-github-pipeworx-io-linear/linear-create-issue.md
What linear_create_issue does on Linear
AI agents use linear_create_issue 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 |
|---|---|---|---|
title | string | Yes | Issue title |
teamId | string | Yes | Team ID to create the issue in |
priority | number | — | Priority level: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low) |
description | string | — | Issue description (markdown supported) |
Parameters from the server's own tool schema.
Why linear_create_issue is rated Medium
This tool creates new records (issues) in Linear, a work management system. Creation is reversible (issues can be deleted), so it falls under Write rather than Destructive. The severity is medium because misuse could create spam, clutter, or false work items, but the impact is limited to project management data and does not affect financial systems, destroy data, or execute arbitrary code.
From the tool's definition Tool name 'linear_create_issue' and description 'Create a new issue in Linear with title and optional description' explicitly indicates data creation.
Attacks that exploit this kind of access
The rule that runs linear_create_issue 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_create_issue, this is the rule to start with:
linear_create_issue 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_create_issue call is checked against it from then on.
Questions about linear_create_issue
Create a new issue in Linear with title and optional description. Returns issue ID, key, title, and URL. 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_create_issue accepts 4 parameters: title, teamId, priority, description. Required: title, teamId. 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_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. 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 server (https://gateway.pipeworx.io/linear/mcp). 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