m365_search_emails
Use this when the user wants to find emails in their Microsoft 365 / Outlook mailbox via the cloud — requires a connected M365 account. Searches by keyword, sender, or subject. For accounts added to the Mac's Mail.app, use search_emails.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-search-emails.md
What m365_search_emails does on Local
AI agents call m365_search_emails 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 |
|---|---|---|---|
limit | integer | — | Max results (default 20, max 50) |
query | string | Yes | Search query, e.g. 'budget Q2', 'from:alice@contoso.com', 'subject:invoice' |
Parameters from the server's own tool schema.
Why m365_search_emails is rated Low
This tool retrieves email data from a Microsoft 365 mailbox without modifying, deleting, or executing anything. It is a straightforward read operation that queries email metadata and content. The requirement for a connected M365 account is a permission control, not a category elevation. Severity is low because email search is a standard, safe operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name contains 'search' and description states it 'finds emails' and 'searches by keyword, sender, or subject' — pure query operations with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs m365_search_emails 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_emails, this is the rule to start with:
m365_search_emails 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_emails call is checked against it from then on.
Questions about m365_search_emails
Use this when the user wants to find emails in their Microsoft 365 / Outlook mailbox via the cloud — requires a connected M365 account. Searches by keyword, sender, or subject. For accounts added to the Mac's Mail.app, use search_emails. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
m365_search_emails accepts 2 parameters: limit, 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_emails: 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_emails 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_emails 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_emails. 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_emails 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