This record as markdown: /tools/0xka13b-microsoft-mcps/move-email.md
What move_email does on Microsoft MCP
AI agents use move_email to create or update resources in Microsoft MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email_id | string | Yes | Message ID to move |
destination_folder | string | Yes | Destination folder name (inbox, sent, drafts, deleted, junk, archive) or folder ID |
Parameters from the server's own tool schema.
Why move_email is rated Medium
Moving emails modifies their organizational state (folder membership) reversibly. This is a write operation rather than read (no data retrieval), execute (no code/command execution), destructive (email is not deleted), or financial.
From the tool's definition Tool performs 'move an email to a different folder' - a reversible modification of email data. Email is relocated but not deleted or destroyed; the action can be undone by moving the email back to its original folder.
Attacks that exploit this kind of access
The rule that runs move_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Microsoft MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_email, this is the rule to start with:
move_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 Microsoft MCP, apply this rule, and every move_email call is checked against it from then on.
Questions about move_email
Move an email to a different folder. It is categorised as a Write tool in the Microsoft MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
move_email accepts 2 parameters: email_id, destination_folder. Required: email_id, destination_folder. The full parameter table on this page comes from the server's own tool schema.
Register the Microsoft MCP server in PolicyLayer and add a rule for move_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 Microsoft MCP. Nothing to install.
move_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 move_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 move_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.
move_email is provided by the Microsoft MCP server (0xka13b/microsoft-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Microsoft, and thousands of servers like it.
This server
Across the catalogue