linear_get_user_issues

Retrieves issues assigned to a specific user or the authenticated user if no userId is provided. Returns issues sorted by last updated, including priority, status, and other metadata. Useful for finding a user

Server Linear MCP Server veddnd/l-mcp
Category Read
Risk class Low
Parameters 00 required

What linear_get_user_issues does on Linear MCP Server

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

Why linear_get_user_issues needs a policy

This tool queries and retrieves data about issues from the Linear system without any side effects. It is a read-only operation that fetches metadata about assigned issues. No data is created, modified, deleted, or external code is executed. This is a low-severity information retrieval operation.

From the tool's definition Tool name and description indicate retrieval: 'Retrieves issues assigned to a specific user' with 'Returns issues sorted by last updated'. No modification, deletion, or execution mentioned.

Questions about linear_get_user_issues

What does the linear_get_user_issues tool do? +

Retrieves issues assigned to a specific user or the authenticated user if no userId is provided. Returns issues sorted by last updated, including priority, status, and other metadata. Useful for finding a user. It is categorised as a Read tool in the Linear MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_get_user_issues? +

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

What risk level is linear_get_user_issues? +

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

Can I rate-limit linear_get_user_issues? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.