get_m365_person
Get detailed information about a specific person in your Microsoft 365 directory by their user ID or email address. Use 'me' to get the currently authenticated user's profile.
This record as markdown: /tools/com-local-mcp-local-mcp/get-m365-person.md
What get_m365_person does on Local
AI agents call get_m365_person to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | User ID (GUID), email address (UPN), or 'me' for the authenticated user, e.g. 'sarah@contoso.com', 'a1b2c3d4-...', or 'me' |
Parameters from the server's own tool schema.
Why get_m365_person is rated Low
This tool retrieves and queries directory/profile data without creating, modifying, deleting, or executing external operations. It is a straightforward read operation on existing contact/person information, typical of directory lookup functionality.
From the tool's definition Tool description states 'Get detailed information about a specific person' and 'Get...profile' — both indicative of data retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_m365_person safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_m365_person, this is the rule to start with:
get_m365_person 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 Local, apply this rule, and every get_m365_person call is checked against it from then on.
Questions about get_m365_person
Get detailed information about a specific person in your Microsoft 365 directory by their user ID or email address. Use 'me' to get the currently authenticated user's profile. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
get_m365_person accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for get_m365_person: 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 Local. Nothing to install.
get_m365_person 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 get_m365_person 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 get_m365_person. 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.
get_m365_person is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue