m365_search_contacts
Search contacts in your Microsoft 365 address book by name, email, or company.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-search-contacts.md
What m365_search_contacts does on Local
AI agents call m365_search_contacts 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 |
|---|---|---|---|
query | string | Yes | Search term — name, email, or company |
Parameters from the server's own tool schema.
Why m365_search_contacts is rated Low
This tool performs a read-only query operation against a contact directory. It retrieves existing data without creating, modifying, deleting, or executing any actions. The severity is low because contact search results present minimal risk—exposure of contact metadata is a lower-impact read operation compared to financial or destructive actions.
From the tool's definition Tool description states 'Search contacts in your Microsoft 365 address book by name, email, or company.' The verb 'search' and the operation of querying contact information are retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs m365_search_contacts 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_search_contacts, this is the rule to start with:
m365_search_contacts 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_search_contacts call is checked against it from then on.
Questions about m365_search_contacts
Search contacts in your Microsoft 365 address book by name, email, or company. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
m365_search_contacts accepts 1 parameter: query. Required: query. 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_search_contacts: 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_search_contacts 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_search_contacts 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_search_contacts. 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_search_contacts 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