linear_getIssueHistory
Get the history of changes made to an issue
This record as markdown: /tools/linear/linear-getissuehistory.md
What linear_getIssueHistory does on Linear
AI agents call linear_getIssueHistory 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 history events to return (default: 10) |
issueId | string | — | ID or identifier of the issue (e.g., ABC-123) |
Parameters from the server's own tool schema.
Why linear_getIssueHistory is rated Low
This tool retrieves historical information about an issue's changes. It is a read-only operation that queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only gain visibility into issue history, not modify systems or access sensitive data beyond what the issue already exposes.
From the tool's definition Tool name 'getIssueHistory' and description 'Get the history of changes made to an issue' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs linear_getIssueHistory 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_getIssueHistory, this is the rule to start with:
linear_getIssueHistory 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_getIssueHistory call is checked against it from then on.
Questions about linear_getIssueHistory
Get the history of changes made to an issue. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getIssueHistory accepts 2 parameters: limit, issueId. 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_getIssueHistory: 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_getIssueHistory 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_getIssueHistory 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_getIssueHistory. 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_getIssueHistory 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