linear_get_issue
Get full details of a Linear issue by ID (e.g., "ABC-123"). Returns title, description, state, priority, assignee, labels, comments, and URL.
This record as markdown: /tools/io-github-pipeworx-io-linear/linear-get-issue.md
What linear_get_issue does on Linear
AI agents call linear_get_issue 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 |
|---|---|---|---|
id | string | Yes | Issue identifier (e.g., "ABC-123") |
Parameters from the server's own tool schema.
Why linear_get_issue is rated Low
This tool retrieves and queries issue data from Linear without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects. Severity is low because unauthorized access to issue details poses minimal risk compared to write or destructive operations, though it could expose sensitive information depending on issue contents.
From the tool's definition Tool description states it 'Get[s] full details of a Linear issue by ID' and 'Returns title, description, state, priority, assignee, labels, comments, and URL.' The verb 'Get' and the list of returned fields (no modification actions mentioned) indicate…
Attacks that exploit this kind of access
The rule that runs linear_get_issue 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_get_issue, this is the rule to start with:
linear_get_issue 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_get_issue call is checked against it from then on.
Questions about linear_get_issue
Get full details of a Linear issue by ID (e.g., "ABC-123"). Returns title, description, state, priority, assignee, labels, comments, and URL. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_get_issue accepts 1 parameter: id. Required: id. 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_get_issue: 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_get_issue 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_get_issue 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_get_issue. 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_get_issue 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