linear_get_user_by_email

Look up a Linear organization member by their email address

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/linear-get-user-by-email.md

WHAT IT DOES

What linear_get_user_by_email does on Sage MCP

AI agents call linear_get_user_by_email to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why linear_get_user_by_email is rated Low

This tool retrieves user information from a Linear organization based on an email address. It performs a read-only query without creating, modifying, deleting, or executing anything. The blast radius is minimal—exposure allows an attacker to discover which email addresses are members of a Linear organization, which is low-sensitivity organizational metadata.

From the tool's definition Tool name 'linear_get_user_by_email' and description 'Look up a Linear organization member by their email address' indicate a query/lookup operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_get_user_by_email safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_get_user_by_email, this is the rule to start with:

linear_get_user_by_email Allowed

linear_get_user_by_email is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_get_user_by_email": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every linear_get_user_by_email call is checked against it from then on.

FAQ

Questions about linear_get_user_by_email

What does the linear_get_user_by_email tool do? +

Look up a Linear organization member by their email address. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_get_user_by_email? +

Register the Sage MCP server in PolicyLayer and add a rule for linear_get_user_by_email: 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 Sage MCP. Nothing to install.

What risk level is linear_get_user_by_email? +

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

Can I rate-limit linear_get_user_by_email? +

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

Set action: deny in the PolicyLayer policy for linear_get_user_by_email. 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_by_email? +

linear_get_user_by_email is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →