This record as markdown: /tools/linear/get-user.md
What get_user does on Linear
AI agents call get_user 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 |
|---|---|---|---|
query | string | — | The UUID or name of the user to retrieve |
Parameters from the server's own tool schema.
Why get_user is rated Low
This tool fetches user information without creating, modifying, deleting, or executing actions. It is a simple data retrieval operation. Severity is low because user profile information is typically non-sensitive or already accessible to authenticated users within a Linear workspace.
From the tool's definition Tool name is 'get_user' and description states 'Retrieve details of a specific Linear user' — both indicate a read-only retrieval operation with no side effects.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs get_user 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 get_user, this is the rule to start with:
get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every get_user call is checked against it from then on.
Questions about get_user
Retrieve details of a specific Linear user. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
get_user accepts 1 parameter: query. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for get_user: 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.
get_user 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 get_user 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 get_user. 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.
get_user 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.
More on Linear, and thousands of servers like it.
This server
Across the catalogue