This record as markdown: /tools/linear/list-issues.md
What list_issues does on Linear
AI agents call list_issues 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 |
|---|---|---|---|
team | string | — | The team name or ID to filter by |
after | string | — | An ID to start from |
cycle | string | — | The cycle name or ID to filter by |
label | string | — | A label name or ID to filter by |
limit | number | — | The number of results to return (Max is 250) |
query | string | — | Search for content in the issue title or description |
state | string | — | The state name or ID to filter by |
before | string | — | An ID to end at |
orderBy | string | — | The order in which to return results |
project | string | — | The project name or ID to filter by |
assignee | string | — | The assignee name or ID to filter by |
delegate | string | — | An agent name or ID to filter by |
Parameters from the server's own tool schema.
Why list_issues is rated Low
This tool queries and returns a list of issues from Linear without creating, modifying, deleting, or executing any actions. It is a straightforward read operation that retrieves data from the workspace. Severity is low because listing issues exposes organizational data but does not compromise systems or enable destructive actions.
From the tool's definition Tool name 'list_issues' and description 'List issues in the user's Linear workspace' indicate a retrieval operation with no modification or side effects.
Risk signalsAccepts freeform code/query input (query) · High parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs list_issues 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_issues, this is the rule to start with:
list_issues 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_issues call is checked against it from then on.
Questions about list_issues
List issues in the user's Linear workspace. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
list_issues accepts 12 parameters: team, after, cycle, label, limit, query, state, before, orderBy, project, assignee, delegate. 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_issues: 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_issues 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_issues 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_issues. 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_issues 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