This record as markdown: /tools/linear/create-issue-label.md
What create_issue_label does on Linear
AI agents use create_issue_label 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 |
|---|---|---|---|
name | string | — | The name of the label |
color | string | — | The color of the label (hex color code) |
teamId | string | — | The team UUID. If not provided, the label will be created as a workspace label |
isGroup | boolean | — | Whether this is label group (cannot be applied to issues directly) |
parentId | string | — | The parent label UUID, if this is a child of a label group |
description | string | — | An optional description of the label |
Parameters from the server's own tool schema.
Why create_issue_label is rated Medium
This tool creates a new label, which is a reversible write operation. It adds metadata to a Linear workspace without deleting or modifying existing data. The severity is medium because creating labels has limited scope (organizational metadata) but could be misused to spam labels or confuse issue organization. It is not critical because labels don't contain sensitive data and can be deleted.
From the tool's definition Tool name is 'create_issue_label' and description states 'Create a new Linear issue label', indicating a create/write operation that adds a new label resource to a Linear workspace.
Attacks that exploit this kind of access
The rule that runs create_issue_label 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 create_issue_label, this is the rule to start with:
create_issue_label 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 create_issue_label call is checked against it from then on.
Questions about create_issue_label
Create a new Linear issue label. 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.
create_issue_label accepts 6 parameters: name, color, teamId, isGroup, parentId, description. 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 create_issue_label: 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.
create_issue_label 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_label 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_label. 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_label is provided by the Linear MCP server (@linear-mcp-server). 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