update_email
Update email properties such as read status, categories, or flag.
This record as markdown: /tools/0xka13b-microsoft-mcps/update-email.md
What update_email does on Microsoft MCP
AI agents use update_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 |
|---|---|---|---|
updates | object | Yes | Properties to update, e.g. {"isRead": true, "categories": ["work"]} |
email_id | string | Yes | Message ID to update |
Parameters from the server's own tool schema.
Why update_email is rated Medium
Updating email properties (read status, categories, flags) is a reversible modification operation that changes existing data state. This falls under the Write category rather than Read (which would only retrieve data) or Destructive (which cannot be undone).
From the tool's definition Tool description explicitly states it can "Update email properties such as read status, categories, or flag." This modifies email metadata fields reversibly without deleting or creating new messages.
Attacks that exploit this kind of access
The rule that runs update_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 update_email, this is the rule to start with:
update_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 update_email call is checked against it from then on.
Questions about update_email
Update email properties such as read status, categories, or flag. 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.
update_email accepts 2 parameters: updates, email_id. Required: updates, email_id. 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 update_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.
update_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 update_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 update_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.
update_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