Low Risk

linear_getIssues

Get a list of recent issues from Linear

How to control linear_getIssues ↓

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

Low Risk

This tool retrieves or queries data (issues) from Linear without creating, modifying, deleting, or executing any actions. It is a straightforward read operation with minimal security risk even if misused by an AI agent, as it only exposes existing issue data that an authenticated user would have access to.

From the tool's definition Tool name 'linear_getIssues' and description 'Get a list of recent issues from Linear' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access linear_getIssues gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Linear, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_getIssues:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_getIssues": {}
  }
}

linear_getIssues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Linear — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the linear_getIssues tool do? +

Get a list of recent issues from Linear. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_getIssues? +

Register the Linear MCP server in PolicyLayer and add a rule for linear_getIssues: 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.

What risk level is linear_getIssues? +

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

Can I rate-limit linear_getIssues? +

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

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

linear_getIssues is provided by the Linear MCP server (tacticlaunch/mcp-linear). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linear tool call.

Deterministic rules across all 182 Linear tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

182 Linear tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.