AI agents use emailrules_move_bottom 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.
Email rule modification is a Write-category action because it creates or modifies email filtering/organization settings reversibly. The 'move' operation suggests reordering rules rather than deletion. Severity is medium because misconfiguration could disrupt email filtering for the account holder, but effects are reversible.
From the tool's definition Tool name 'emailrules_move_bottom' indicates modification of email rule ordering/configuration. The 'move' operation on email rules suggests reordering or repositioning rules, which are reversible configuration changes.
Attacks that exploit this kind of access
emailrules_move_bottom. 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 emailrules_move_bottom: 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.
emailrules_move_bottom 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 emailrules_move_bottom 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 emailrules_move_bottom. 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.
emailrules_move_bottom 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 →