send_email
Use this when the user wants to send an email from an account configured in the Mac's Apple Mail. Composes and sends via Mail.app; supports plain text or HTML body. For sending from a Microsoft 365 account NOT added to Mail.app, use m365_send_email. Pass from to send from a specific configured Ma...
This record as markdown: /tools/com-local-mcp-local-mcp/send-email.md
What send_email does on Local
AI agents use send_email to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cc | string | — | |
to | string | Yes | |
bcc | string | — | |
body | string | — | |
from | string | — | |
confirm | boolean | — | |
subject | string | Yes | |
html_body | string | — | |
attachments | string | — |
Parameters from the server's own tool schema.
Why send_email is rated Medium
This tool creates and sends emails, which is a Write operation (creates new data/communications). It is not Read (no retrieval), not Execute (not running arbitrary code), not Destructive (emails sent are not irreversibly deleted from user's control), not Financial.
From the tool's definition Tool description explicitly states 'Composes and sends via Mail.app' and 'sends an email from an account configured in the Mac's Apple Mail', indicating irreversible creation of outbound communications.
Risk signalsAccepts raw HTML/template content (body)
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 Local, 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 Local, apply this rule, and every send_email call is checked against it from then on.
Questions about send_email
Use this when the user wants to send an email from an account configured in the Mac's Apple Mail. Composes and sends via Mail.app; supports plain text or HTML body. For sending from a Microsoft 365 account NOT added to Mail.app, use m365_send_email. Pass from to send from a specific configured Mail.app account instead of the default sender. Pass attachments as a comma-separated list of absolute file paths to attach files. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
send_email accepts 9 parameters: cc, to, bcc, body, from, confirm, subject, html_body, attachments. Required: to, subject. The full parameter table on this page comes from the server's own tool schema.
Register the Local 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 Local. 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 Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue