This record as markdown: /tools/linear/linear-searchissues.md
What linear_searchIssues does on Linear
AI agents call linear_searchIssues 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 issues to return (default: 10) |
query | string | — | Text to search for in issue title or description |
states | array | — | Filter issues by state name (e.g., 'Todo', 'In Progress', 'Done') |
teamId | string | — | Filter issues by team ID |
projectId | string | — | Filter issues by project ID |
assigneeId | string | — | Filter issues by assignee ID |
Parameters from the server's own tool schema.
Why linear_searchIssues is rated Low
This tool searches and retrieves issue data based on filter criteria. It has no side effects—it does not create, modify, delete, or execute operations. It is purely a data retrieval function, consistent with the Read category for tools like search, list, get, and fetch.
From the tool's definition Tool name 'searchIssues' and description 'Search for issues with various filters' indicate a query operation that retrieves data without modifying it.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs linear_searchIssues 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_searchIssues, this is the rule to start with:
linear_searchIssues 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_searchIssues call is checked against it from then on.
Questions about linear_searchIssues
Search for issues with various filters. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_searchIssues accepts 6 parameters: limit, query, states, teamId, projectId, assigneeId. 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_searchIssues: 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_searchIssues 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_searchIssues 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_searchIssues. 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_searchIssues 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