linear_getProjectIssues
Get all issues associated with a project
This record as markdown: /tools/linear/linear-getprojectissues.md
What linear_getProjectIssues does on Linear
AI agents call linear_getProjectIssues 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 |
|---|---|---|---|
limit | number | — | Maximum number of issues to return (default: 25) |
projectId | string | — | ID of the project to get issues for |
Parameters from the server's own tool schema.
Why linear_getProjectIssues is rated Low
This tool queries and retrieves existing data (issues from a project) without modifying, deleting, or executing any operations. It is a straightforward read operation analogous to 'get' or 'list' verbs, making it a Read category risk with low severity since information disclosure about project issues has minimal blast radius unless the issues contain highly sensitive data.
From the tool's definition Tool name 'getProjectIssues' and description 'Get all issues associated with a project' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs linear_getProjectIssues 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_getProjectIssues, this is the rule to start with:
linear_getProjectIssues 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_getProjectIssues call is checked against it from then on.
Questions about linear_getProjectIssues
Get all issues associated with a project. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getProjectIssues accepts 2 parameters: limit, projectId. 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_getProjectIssues: 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_getProjectIssues 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_getProjectIssues 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_getProjectIssues. 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_getProjectIssues 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