get_issue

Get detailed information about a specific issue by its ID

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/get-issue.md

WHAT IT DOES

What get_issue does on Linear Kanban Server

AI agents call get_issue 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 get_issue is rated Low

This tool retrieves or queries existing issue data without creating, modifying, deleting, or executing any actions. It is a pure read operation typical of data retrieval endpoints. The low severity reflects minimal blast radius—at worst, an agent could retrieve information about issues it shouldn't have access to, but no data is altered or destroyed.

From the tool's definition Tool name 'get_issue' and description 'Get detailed information about a specific issue by its ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_issue 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 get_issue, this is the rule to start with:

get_issue Allowed

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

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 get_issue call is checked against it from then on.

FAQ

Questions about get_issue

What does the get_issue tool do? +

Get detailed information about a specific issue by its ID. 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 get_issue? +

Register the Linear Kanban Server MCP server in PolicyLayer and add a rule for get_issue: 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 get_issue? +

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

Can I rate-limit get_issue? +

Yes. Add a rate_limit block to the get_issue 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 get_issue completely? +

Set action: deny in the PolicyLayer policy for get_issue. 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 get_issue? +

get_issue 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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