AI agents call issue_states to retrieve information from Linear without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workflow state information from Linear without modifying any data. It's a read-only query operation with minimal blast radius.
From the tool's definition Get all available issue states (workflow states) in Linear
Attacks that exploit this kind of access
Get all available issue states (workflow states) in Linear. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP server in PolicyLayer and add a rule for issue_states: 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.
issue_states 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 issue_states 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 issue_states. 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.
issue_states is provided by the Linear MCP server (mkusaka/mcp-server-linear). 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 →