# linear_create_issue

Create a new issue in Linear with title and optional description. Returns issue ID, key, title, and URL.

Agent View of the PolicyLayer registry record for `linear_create_issue`. HTML page: https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-create-issue

## Facts

- Tool: `linear_create_issue`
- Server: Linear (`https://gateway.pipeworx.io/linear/mcp`) — https://policylayer.com/tools/io-github-pipeworx-io-linear.md
- Homepage: https://github.com/pipeworx-io/mcp-linear
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: yes
- Parameters: 4 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | yes | Issue title |
| `teamId` | string | yes | Team ID to create the issue in |
| `priority` | number | no | Priority level: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low) |
| `description` | string | no | Issue description (markdown supported) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "linear_create_issue",
    "arguments": {
      "title": "<title>",
      "teamId": "<teamId>"
    }
  }
}
```

## 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 own definition: "Tool name 'linear_create_issue' and description 'Create a new issue in Linear with title and optional description' explicitly indicates data creation."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Linear:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_create_issue": {
      "limits": [
        {
          "counter": "linear_create_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Linear (35)

- `forget` — Destructive — https://policylayer.com/tools/io-github-pipeworx-io-linear/forget.md
- `generate_llms_txt` — Execute — https://policylayer.com/tools/io-github-pipeworx-io-linear/generate-llms-txt.md
- `polymarket_edges` — Financial — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-edges.md
- `polymarket_fill_risk` — Financial — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-fill-risk.md
- `ai_visibility_check` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ai-visibility-check.md
- `ask_pipeworx` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ask-pipeworx.md
- `ask_pipeworx_beta` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ask-pipeworx-beta.md
- `ask_pipeworx_grounded` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ask-pipeworx-grounded.md
- `bet_research` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/bet-research.md
- `compare_entities` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/compare-entities.md
- `deep_research` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/deep-research.md
- `discover_tools` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/discover-tools.md
- `entity_profile` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/entity-profile.md
- `linear_get_issue` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-get-issue.md
- `linear_list_issues` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-list-issues.md
- `linear_list_teams` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-list-teams.md
- `linear_search` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-search.md
- `list_subscriptions` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/list-subscriptions.md
- `pipeworx_trending` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/pipeworx-trending.md
- `polymarket_arbitrage` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-arbitrage.md
- `polymarket_edge_tracker` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-edge-tracker.md
- `polymarket_kalshi_spread` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-kalshi-spread.md
- `recall` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/recall.md
- `recent_alerts` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/recent-alerts.md
- `recent_changes` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/recent-changes.md
- `resolve_entity` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/resolve-entity.md
- `scan_competitor_ai_presence` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/scan-competitor-ai-presence.md
- `scan_dependency` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/scan-dependency.md
- `search_within` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/search-within.md
- `suggest_questions` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/suggest-questions.md
- …and 5 more: https://policylayer.com/tools/io-github-pipeworx-io-linear.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-pipeworx-io-linear · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-pipeworx-io-linear