AI agents call linear_search_issues to retrieve information from MCP-GET without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation to retrieve Linear issues matching specified criteria. It has no capability to create, modify, delete, or execute operations—it purely queries and returns data. The blast radius of misuse is minimal; worst case would be exposure of issue titles or descriptions that an AI agent might already have access to via other read operations.
From the tool's definition Tool name 'linear_search_issues' and description 'Search for Linear issues by title or description' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Search for Linear issues by title or description. It is categorised as a Read tool in the MCP-GET MCP Server, which means it retrieves data without modifying state.
Register the MCP-GET MCP server in PolicyLayer and add a rule for linear_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 MCP-GET. Nothing to install.
linear_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 linear_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 linear_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.
linear_search_issues is provided by the MCP-GET MCP server (kennethdsheridan/mcp-get). 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 →