search_issues

Search for issues by title or description text

SERVERLinear Kanban Server SOURCE0xikarus/linear-kanban-mcp

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/0xikarus-linear-kanban-mcp/search-issues.md

WHAT IT DOES

What search_issues does on Linear Kanban Server

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

RISK

Why search_issues is rated Low

This tool retrieves and queries existing issue data based on search criteria. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move resources. It is purely a read/retrieval operation, making it the least severe category.

From the tool's definition Tool name is 'search_issues' and description states it 'Search[es] for issues by title or description text' - a query operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_issues safely

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

search_issues Allowed

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": {
    "search_issues": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Linear Kanban Server, apply this rule, and every search_issues call is checked against it from then on.

FAQ

Questions about search_issues

What does the search_issues tool do? +

Search for issues by title or description text. It is categorised as a Read tool in the Linear Kanban Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_issues? +

Register the Linear Kanban 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 Kanban Server. Nothing to install.

What risk level is search_issues? +

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

Can I rate-limit search_issues? +

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.

How do I block search_issues completely? +

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.

What MCP server provides search_issues? +

search_issues is provided by the Linear Kanban Server MCP server (0xikarus/linear-kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linear Kanban Server, and thousands of servers like it.

This server

All 22 Linear Kanban Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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