Get the history of changes made to an issue
AI agents call linear_getIssueHistory 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 historical data about an issue's changes without creating, modifying, deleting, or executing any operations. It is purely informational and carries no risk of data loss or unintended modifications. Severity is low because reading audit history has minimal blast radius—it cannot damage systems or data if misused by an AI agent.
From the tool's definition Tool name 'linear_getIssueHistory' and description 'Get the history of changes made to an issue' indicate a retrieval operation with no side effects. The verb 'get' and the passive nature of 'history' (an audit trail) confirm read-only functionality.
Attacks that exploit this kind of access
Get the history of changes made to an issue. 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 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 MCP Server. 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 MCP server (wkoutre/linear-mcp-server). 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 →