Get detailed information about a specific Linear issue including optional relationships and cleaned content
AI agents call get_issue to retrieve information from Linear MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves issue data without creating, modifying, or deleting any resources. It has no side effects beyond reading existing information from the Linear issue tracking system. The blast radius of misuse is minimal—an agent could only access issue details it is authorized to view, with no ability to alter state or cause harm.
From the tool's definition Tool name 'get_issue' combined with description 'Get detailed information about a specific Linear issue' indicates data retrieval with no modification. The phrase 'including optional relationships and cleaned content' confirms this is a query operation.
Attacks that exploit this kind of access
Get detailed information about a specific Linear issue including optional relationships and cleaned content. It is categorised as a Read tool in the Linear MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Server 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 MCP Server. 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 MCP server (packetnomad/linear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →