linear_search_issues

Search Linear issues by text query

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/linear-search-issues.md

WHAT IT DOES

What linear_search_issues does on Sage MCP

AI agents call linear_search_issues to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why linear_search_issues is rated Low

This is a search/query tool that retrieves data from Linear's issue tracking system. It performs no mutations, deletions, code execution, or financial operations. The search function is read-only and returns matching results based on the query parameter, with no side effects on the underlying data.

From the tool's definition Tool name 'linear_search_issues' and description 'Search Linear issues by text query' indicate a read-only operation that retrieves issue data without modifying, deleting, or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_search_issues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_search_issues, this is the rule to start with:

linear_search_issues Allowed

linear_search_issues is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_search_issues": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every linear_search_issues call is checked against it from then on.

FAQ

Questions about linear_search_issues

What does the linear_search_issues tool do? +

Search Linear issues by text query. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_search_issues? +

Register the Sage 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 Sage MCP. Nothing to install.

What risk level is linear_search_issues? +

linear_search_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit linear_search_issues? +

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.

How do I block linear_search_issues completely? +

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.

What MCP server provides linear_search_issues? +

linear_search_issues is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →