linear_get_user
Get one user by UUID, including their team memberships.
This record as markdown: /tools/allmcp/linear-get-user.md
What linear_get_user does on Allmcp
AI agents call linear_get_user to retrieve information from Allmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why linear_get_user is rated Low
This tool retrieves user profile and team membership information by UUID. It performs a query operation with no side effects, no data modification, no execution of code, and no financial implications. The 'Get' operation and 'including' language confirm read-only access to existing data.
From the tool's definition Tool name 'linear_get_user' and description 'Get one user by UUID, including their team memberships' indicate retrieval of user information with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs linear_get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_get_user, this is the rule to start with:
linear_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 Allmcp, apply this rule, and every linear_get_user call is checked against it from then on.
Questions about linear_get_user
Get one user by UUID, including their team memberships. It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.
Register the All MCP server in PolicyLayer and add a rule for linear_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 Allmcp. Nothing to install.
linear_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 linear_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 linear_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.
linear_get_user is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue