m365_get_contact
Get full details of a specific Microsoft 365 contact by ID. Get the ID from m365_list_contacts or m365_search_contacts.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-get-contact.md
What m365_get_contact does on Local
AI agents call m365_get_contact 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 | Contact ID from m365_list_contacts or m365_search_contacts |
Parameters from the server's own tool schema.
Why m365_get_contact is rated Low
This tool retrieves contact information from Microsoft 365 without creating, modifying, or deleting data. It is a read-only query operation. Severity is low because contact data retrieval, while potentially sensitive, does not cause irreversible changes or enable financial transactions. The blast radius is limited to information disclosure about a single contact.
From the tool's definition Tool description states 'Get full details of a specific Microsoft 365 contact by ID' — a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs m365_get_contact 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 m365_get_contact, this is the rule to start with:
m365_get_contact 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 m365_get_contact call is checked against it from then on.
Questions about m365_get_contact
Get full details of a specific Microsoft 365 contact by ID. Get the ID from m365_list_contacts or m365_search_contacts. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
m365_get_contact 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 m365_get_contact: 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.
m365_get_contact 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 m365_get_contact 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 m365_get_contact. 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.
m365_get_contact 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