This record as markdown: /tools/linear/linear-getissues.md
What linear_getIssues does on Linear
AI agents call linear_getIssues 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: 10) |
Parameters from the server's own tool schema.
Why linear_getIssues is rated Low
This tool retrieves or lists existing issues without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on Linear's issue data, consistent with the Read category. The blast radius if misused is minimal—an AI agent retrieving issues cannot cause harm beyond potential information disclosure concerns, which are low-severity in a typical organizational context.
From the tool's definition Tool name 'getIssues' and description 'Get a list of recent issues from Linear' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs linear_getIssues 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_getIssues, this is the rule to start with:
linear_getIssues 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_getIssues call is checked against it from then on.
Questions about linear_getIssues
Get a list of recent issues from Linear. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getIssues accepts 1 parameter: limit. 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_getIssues: 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_getIssues 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_getIssues 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_getIssues. 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_getIssues 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