list_my_issues

List issues assigned to the current user

SERVERLinear SOURCE@linear-mcp-server

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/linear/list-my-issues.md

WHAT IT DOES

What list_my_issues does on Linear

AI agents call list_my_issues 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
`after`	string	—	An ID to start from
`limit`	number	—	The number of results to return (Max is 250)
`before`	string	—	An ID to end at
`orderBy`	string	—	The order in which to return results

Parameters from the server's own tool schema.

RISK

Why list_my_issues is rated Low

This tool retrieves a filtered list of issues belonging to the authenticated user. It performs a read-only query against the Linear API with no capability to create, modify, or delete data. The blast radius of misuse is minimal — an attacker could only view issues already assigned to that user account, which is typically already visible in the UI.

From the tool's definition Tool name is 'list_my_issues' and description states 'List issues assigned to the current user' — a clear query/retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_my_issues Allowed

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

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

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

FAQ

Questions about list_my_issues

What does the list_my_issues tool do? +

List issues assigned to the current user. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.

What parameters does list_my_issues accept? +

list_my_issues accepts 4 parameters: after, limit, before, orderBy. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_my_issues? +

Register the Linear MCP server in PolicyLayer and add a rule for list_my_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. Nothing to install.

What risk level is list_my_issues? +

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

Can I rate-limit list_my_issues? +

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

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

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

KEEP EXPLORING

More on Linear, and thousands of servers like it.

This server

All 66 Linear tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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