send_message
Send a new email from an inbox.
This record as markdown: /tools/dev-agenticemail-mcp/send-message.md
What send_message does on AgenticEmail
AI agents use send_message to create or update resources in AgenticEmail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AgenticEmail environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | array | Yes | |
html | string | — | |
text | string | — | |
subject | string | Yes | |
inbox_id | string | Yes |
Parameters from the server's own tool schema.
Why send_message is rated Medium
Sending an email creates and transmits new data, which is a Write operation. It is not Read (does not merely retrieve data), not Execute (does not run arbitrary code or commands), not Destructive (emails sent can theoretically be unsent or are not permanently deleted), and not Financial (no money moves).
From the tool's definition Tool name is 'send_message' and description states it will 'Send a new email from an inbox.' This creates new email data that is sent to external recipients.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs send_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AgenticEmail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_message, this is the rule to start with:
send_message 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 AgenticEmail, apply this rule, and every send_message call is checked against it from then on.
Questions about send_message
Send a new email from an inbox. It is categorised as a Write tool in the AgenticEmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
send_message accepts 5 parameters: to, html, text, subject, inbox_id. Required: to, subject, inbox_id. The full parameter table on this page comes from the server's own tool schema.
Register the AgenticEmail MCP server in PolicyLayer and add a rule for send_message: 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 AgenticEmail. Nothing to install.
send_message 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_message 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_message. 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_message is provided by the AgenticEmail MCP server (https://api.agenticemail.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AgenticEmail, and thousands of servers like it.
This server
Across the catalogue