AI agents use email_reply_all to create or update resources in M365 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your M365 environment.
This tool creates new email messages and sends them on behalf of the user, affecting email records and potentially reaching multiple recipients. While not destructive (emails are not deleted or irreversibly overwritten) and not financial, it is a write operation with significant blast radius if misused—an AI agent could send unintended, inappropriate, or sensitive communications to all recipients in a thread.
From the tool's definition Tool name 'email_reply_all' indicates the ability to compose and send email replies to all recipients of a message thread. This is a write operation that modifies email state by creating and dispatching a new message.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
email_reply_all. It is categorised as a Write tool in the M365 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the M365 MCP server in PolicyLayer and add a rule for email_reply_all: 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 M365. Nothing to install.
email_reply_all 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 email_reply_all 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 email_reply_all. 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.
email_reply_all is provided by the M365 MCP server (robin-collins/m365-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →