linear_search
Search Linear issues by keyword or text. Returns matching issues with ID, title, state, priority, and URL.
This record as markdown: /tools/io-github-pipeworx-io-linear/linear-search.md
What linear_search does on Linear
AI agents call linear_search 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 |
|---|---|---|---|
first | number | — | Number of results to return (default 20, max 50) |
query | string | Yes | Search query text |
Parameters from the server's own tool schema.
Why linear_search is rated Low
This tool retrieves and queries data from Linear's issue tracking system without creating, modifying, deleting, or executing any operations. It has minimal blast radius if misused by an AI agent - worst case being exposure of issue metadata already visible to the authenticated user. This is a standard Read operation.
From the tool's definition Tool description states 'Search Linear issues by keyword or text. Returns matching issues' - this is a retrieval operation with no modification or deletion of data. The verb 'search' and 'returns' indicate query-only functionality.
Attacks that exploit this kind of access
The rule that runs linear_search 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_search, this is the rule to start with:
linear_search 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_search call is checked against it from then on.
Questions about linear_search
Search Linear issues by keyword or text. Returns matching issues with ID, title, state, priority, and URL. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_search accepts 2 parameters: first, query. Required: query. 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_search: 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_search 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 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. 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 is provided by the Linear MCP server (https://gateway.pipeworx.io/linear/mcp). 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