m365_reply_email
Use this when the user wants to reply to a Microsoft 365 email (message ID from m365_list_emails). Requires a connected M365 account. Shows a preview first — set confirm=true to actually send. For replying to a message found in Apple Mail, use reply_email.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-reply-email.md
What m365_reply_email does on Local
AI agents use m365_reply_email to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Message ID to reply to (from m365_list_emails or m365_read_email) |
confirm | boolean | — | Set to true to actually send (default: shows preview only) |
message | string | Yes | Your reply text |
reply_all | boolean | — | If true, reply to all recipients (default: false) |
Parameters from the server's own tool schema.
Why m365_reply_email is rated Medium
This tool writes (composes and sends) email messages, which modifies data in the email system. It is not destructive (emails can be unsent/deleted), not financial, and not execute (it doesn't run arbitrary code).
From the tool's definition Tool performs email reply/send action: 'reply to a Microsoft 365 email', 'set confirm=true to actually send'. This creates and sends new email data.
Attacks that exploit this kind of access
The rule that runs m365_reply_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_reply_email, this is the rule to start with:
m365_reply_email stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_reply_email call is checked against it from then on.
Questions about m365_reply_email
Use this when the user wants to reply to a Microsoft 365 email (message ID from m365_list_emails). Requires a connected M365 account. Shows a preview first — set confirm=true to actually send. For replying to a message found in Apple Mail, use reply_email. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
m365_reply_email accepts 4 parameters: id, confirm, message, reply_all. Required: id, message. 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_reply_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_reply_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the m365_reply_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_reply_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_reply_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