list_issue_labels
List available issue labels in a Linear workspace or team
This record as markdown: /tools/linear/list-issue-labels.md
What list_issue_labels does on Linear
AI agents call list_issue_labels to retrieve information from Linear without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Filter by label name |
team | string | — | The team name or ID |
after | string | — | An ID to start from |
limit | number | — | The number of results to return (Max is 250) |
before | string | — | An ID to end at |
orderBy | string | — | The order in which to return results |
Parameters from the server's own tool schema.
Why list_issue_labels is rated Low
This tool performs a query operation to retrieve and display issue labels. It does not create, modify, delete, or execute any operations—it only reads and lists existing data. The action is informational with no blast radius if misused by an agent.
From the tool's definition Tool name 'list_issue_labels' and description 'List available issue labels in a Linear workspace or team' indicate a read-only query operation that retrieves existing label data with no side effects.
Attacks that exploit this kind of access
The rule that runs list_issue_labels 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 list_issue_labels, this is the rule to start with:
list_issue_labels is read-only, so it stays allowed. 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 list_issue_labels call is checked against it from then on.
Questions about list_issue_labels
List available issue labels in a Linear workspace or team. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
list_issue_labels accepts 6 parameters: name, team, after, limit, before, orderBy. 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 list_issue_labels: 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.
list_issue_labels is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_issue_labels 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 list_issue_labels. 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.
list_issue_labels 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