Moves emails from one folder to another
AI agents use move-emails to create or update resources in Outlook MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook MCP Server environment.
Moving emails between folders is a Write operation: it modifies email metadata (folder location) but is fully reversible by moving the message back to its original folder. It does not delete data (which would be Destructive) nor execute arbitrary code (Execute).
From the tool's definition Tool description states 'Moves emails from one folder to another' - a reversible modification of email state/location without deletion.
Attacks that exploit this kind of access
Moves emails from one folder to another. It is categorised as a Write tool in the Outlook MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outlook MCP Server MCP server in PolicyLayer and add a rule for move-emails: 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 Outlook MCP Server. Nothing to install.
move-emails 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 move-emails 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 move-emails. 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.
move-emails is provided by the Outlook MCP Server MCP server (peacockery-studio/outlook-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 →