Search for Linear issues with various filters
AI agents call search_issues 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 or queries data from Linear issues without creating, modifying, deleting, or executing any operations. It has no side effects and is purely informational, placing it clearly in the Read category with low severity.
From the tool's definition Tool name 'search_issues' and description 'Search for Linear issues with various filters' indicate querying/retrieval operations. The description uses 'search' which is a read operation by definition.
Attacks that exploit this kind of access
Search for Linear issues with various filters. 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 search_issues: 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.
search_issues 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 search_issues 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 search_issues. 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.
search_issues is provided by the Linear MCP Server MCP server (larryhudson/linear-mcp-server-again). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_issues is one line of Linear MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →