AI agents use emailfolders_mark_all_as_read 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 modifies email read status across potentially large numbers of messages. While reversible (emails can be marked unread again), it represents a Write action that changes data state. Severity is medium because the blast radius is limited to email metadata and can be undone; it lacks the irreversibility of Destructive operations or the financial impact of Financial operations.
From the tool's definition Tool name 'emailfolders_mark_all_as_read' indicates a bulk modification operation on email folder state. The 'mark_as_read' action modifies email metadata (read/unread status) across potentially all emails in a folder.
Attacks that exploit this kind of access
emailfolders_mark_all_as_read. 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 emailfolders_mark_all_as_read: 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.
emailfolders_mark_all_as_read 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 emailfolders_mark_all_as_read 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 emailfolders_mark_all_as_read. 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.
emailfolders_mark_all_as_read 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 →