get_issue
Retrieve detailed information about an issue by ID, including attachments and git branch name
This record as markdown: /tools/linear/get-issue.md
What get_issue does on Linear
AI agents call 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 | — | The issue ID |
Parameters from the server's own tool schema.
Why get_issue is rated Low
This tool retrieves issue details (attachments, git branch name, etc.) without creating, modifying, deleting, or executing operations. It is a straightforward read-only query operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_issue' and description 'Retrieve detailed information about an issue by ID' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs 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 get_issue, this is the rule to start with:
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 get_issue call is checked against it from then on.
Questions about get_issue
Retrieve detailed information about an issue by ID, including attachments and git branch name. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
get_issue accepts 1 parameter: 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 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.
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 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 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.
get_issue 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