linear_getViewer
Get information about the currently authenticated user
This record as markdown: /tools/linear/linear-getviewer.md
What linear_getViewer does on Linear
AI agents call linear_getViewer 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.
Why linear_getViewer is rated Low
This tool performs a read-only operation to fetch metadata about the authenticated user. It has no side effects, cannot modify any data, and presents minimal risk. The blast radius is very small as it only exposes information already available to the authenticated session. Classified as Read with low severity.
From the tool's definition Tool name 'getViewer' and description 'Get information about the currently authenticated user' indicate a query operation that retrieves user data without modification.
Attacks that exploit this kind of access
The rule that runs linear_getViewer 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 linear_getViewer, this is the rule to start with:
linear_getViewer 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 linear_getViewer call is checked against it from then on.
Questions about linear_getViewer
Get information about the currently authenticated user. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP server in PolicyLayer and add a rule for linear_getViewer: 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.
linear_getViewer 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_getViewer 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_getViewer. 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_getViewer 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