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.
This tool queries and retrieves existing issue data assigned to a specific user. It performs a read-only operation without creating, modifying, deleting, or executing any actions. The retrieval of project management metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'linear_get_user_issues' and description 'Get issues assigned to a user' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access linear_get_user_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linear MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_get_user_issues:
{
"version": "1",
"default": "deny",
"tools": {
"linear_get_user_issues": {}
}
}linear_get_user_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get issues assigned to a user. It is categorised as a Read tool in the Linear MCP Server MCP Server, which means it retrieves data without modifying state.
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.
linear_get_user_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
linear_get_user_issues is provided by the Linear MCP Server MCP server (vinayak-mehta/linear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linear MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Linear MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.