teams_get_user_by_email
Look up a Microsoft 365 user by email address using Microsoft Graph
This record as markdown: /tools/sagemcp-sagemcp/teams-get-user-by-email.md
What teams_get_user_by_email does on Sage MCP
AI agents call teams_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.
Why teams_get_user_by_email is rated Low
This tool retrieves user information from Microsoft 365 via the Graph API. While classified as Read (no data modification), the severity is elevated to medium because: (1) user directory information can be sensitive and expose organizational structure, (2) unauthorized enumeration of users by email could enable targeted attacks or social engineering, and (3) in a multi-tenant platform, proper access controls are…
From the tool's definition Tool description states 'Look up a Microsoft 365 user by email address' — a retrieval operation with no modification or side effects. The tool name 'get_user_by_email' also confirms a read/query pattern.
Attacks that exploit this kind of access
The rule that runs teams_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 teams_get_user_by_email, this is the rule to start with:
teams_get_user_by_email 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 Sage MCP, apply this rule, and every teams_get_user_by_email call is checked against it from then on.
Questions about teams_get_user_by_email
Look up a Microsoft 365 user by email address using Microsoft Graph. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for teams_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.
teams_get_user_by_email 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 teams_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.
Set action: deny in the PolicyLayer policy for teams_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.
teams_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.
More on Sage, and thousands of servers like it.
This server
Across the catalogue