m365_list_emails
Use this when the user wants their Microsoft 365 / Outlook / Exchange inbox via the cloud — requires a connected M365 account (connect_m365_account). Returns subject, sender, date, and preview. For mail already in the Mac's Mail.app (including an Exchange account added there), use list_emails.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-list-emails.md
What m365_list_emails does on Local
AI agents call m365_list_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 | — | Number of emails to return (default 20, max 50) |
folder | string | — | Folder name: inbox (default), sentitems, drafts, deleteditems |
unread_only | boolean | — | If true, return only unread emails |
Parameters from the server's own tool schema.
Why m365_list_emails is rated Low
This tool retrieves and queries email data from Microsoft 365 without creating, modifying, deleting, or executing any operations. It is purely informational, returning read-only email metadata. The low severity reflects minimal blast radius—an agent could retrieve sensitive email content, but cannot alter mailboxes, execute code, or cause irreversible damage.
From the tool's definition Tool name 'm365_list_emails' and description 'Returns subject, sender, date, and preview' indicate data retrieval only. The description explicitly states it returns email metadata without modification: 'subject, sender, date, and preview'.
Risk signalsAccepts file system path (folder)
Attacks that exploit this kind of access
The rule that runs m365_list_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_list_emails, this is the rule to start with:
m365_list_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_list_emails call is checked against it from then on.
Questions about m365_list_emails
Use this when the user wants their Microsoft 365 / Outlook / Exchange inbox via the cloud — requires a connected M365 account (connect_m365_account). Returns subject, sender, date, and preview. For mail already in the Mac's Mail.app (including an Exchange account added there), use list_emails. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
m365_list_emails accepts 3 parameters: limit, folder, unread_only. 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_list_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_list_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_list_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_list_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_list_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