linear_list_issues
Browse issues in your Linear workspace with optional filters by state, priority, or assignee. Returns issue ID, title, state, priority, assignee, and URL.
This record as markdown: /tools/io-github-pipeworx-io-linear/linear-list-issues.md
What linear_list_issues does on Linear
AI agents call linear_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 |
|---|---|---|---|
first | number | — | Number of issues to return (default 20, max 50) |
filter | string | — | Optional filter object as JSON string (e.g., {"state":{"name":{"eq":"In Progress"}}}). Passed directly to the Linear issues query filter. |
Parameters from the server's own tool schema.
Why linear_list_issues is rated Low
This tool retrieves and queries data from a Linear workspace with optional filtering parameters. It has no capability to create, modify, delete, or execute operations. The output is read-only metadata about issues. This is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent—at worst, an attacker could enumerate issues to which they already have access.
From the tool's definition Tool description states it "Browse[s] issues" and "Returns issue ID, title, state, priority, assignee, and URL" — purely retrieval operations with no mention of modification, deletion, or execution of side effects.
Attacks that exploit this kind of access
The rule that runs linear_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 linear_list_issues, this is the rule to start with:
linear_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 linear_list_issues call is checked against it from then on.
Questions about linear_list_issues
Browse issues in your Linear workspace with optional filters by state, priority, or assignee. Returns issue ID, title, state, priority, assignee, and URL. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_list_issues accepts 2 parameters: first, filter. 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_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.
linear_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 linear_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 linear_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.
linear_list_issues 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