Look up a Microsoft 365 user by email address using Microsoft Graph
AI agents call teams_get_user_by_email to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access teams_get_user_by_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for teams_get_user_by_email:
{
"version": "1",
"default": "deny",
"tools": {
"teams_get_user_by_email": {}
}
}teams_get_user_by_email is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.