m365_read_email
Use this when the user wants the full content of a Microsoft 365 email (message ID from m365_list_emails/m365_search_emails). Requires a connected M365 account. For a message found via list_emails/search_emails (Apple Mail), use read_email.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-read-email.md
What m365_read_email does on Local
AI agents call m365_read_email 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 | The email message ID from m365_list_emails or m365_search_emails |
Parameters from the server's own tool schema.
Why m365_read_email is rated Low
This tool retrieves and queries email data with no side effects. It takes a message ID parameter and returns email content, matching the Read category definition (retrieves or queries data; no side effects). Severity is low because email retrieval is a standard, non-destructive operation with limited blast radius—misuse would result in information disclosure rather than system damage or data loss.
From the tool's definition Tool name contains 'read_email' and description states 'Use this when the user wants the full content of a Microsoft 365 email', explicitly retrieving email message content without modification.
Attacks that exploit this kind of access
The rule that runs m365_read_email 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_read_email, this is the rule to start with:
m365_read_email 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_read_email call is checked against it from then on.
Questions about m365_read_email
Use this when the user wants the full content of a Microsoft 365 email (message ID from m365_list_emails/m365_search_emails). Requires a connected M365 account. For a message found via list_emails/search_emails (Apple Mail), use read_email. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
m365_read_email 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_read_email: 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_read_email 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_read_email 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_read_email. 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_read_email 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