This record as markdown: /tools/0xka13b-microsoft-mcps/send-email.md
What send_email does on Microsoft MCP
AI agents use send_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 |
|---|---|---|---|
cc | array | — | CC recipients |
to | array | Yes | Recipient email addresses |
bcc | array | — | BCC recipients |
body | string | Yes | Email body |
subject | string | Yes | Email subject |
body_type | string | — | Body content type. Defaults to text. |
attachments | array | — | File attachments |
Parameters from the server's own tool schema.
Why send_email is rated Medium
This tool creates and commits a new email message to the system. While sending an email is technically irreversible (cannot be unsent in most email systems), it is classified as Write rather than Destructive because the action is creating/modifying data (composing and transmitting a message) rather than permanently deleting or overwriting existing data.
From the tool's definition Tool performs 'Send an email immediately' — creates and transmits a message, which is a reversible but irreversible communication action that modifies the email system state.
Risk signalsAccepts raw HTML/template content (body) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs send_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 send_email, this is the rule to start with:
send_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 send_email call is checked against it from then on.
Questions about send_email
Send an email immediately. 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.
send_email accepts 7 parameters: cc, to, bcc, body, subject, body_type, attachments. Required: to, body, subject. 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 send_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.
send_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 send_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 send_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.
send_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