messages_send_email
Compose and send an email — with subject, CC/BCC, and attachments. Use for email; for chat messages (Telegram/WhatsApp/livechat) use messages.send instead.
This record as markdown: /tools/io-github-saloprj-dialogbrain/messages-send-email.md
What messages_send_email does on Dialogbrain
AI agents use messages_send_email to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cc | array | — | Email addresses to CC. OMIT to skip. |
bcc | array | — | Email addresses to BCC. OMIT to skip. |
text | string | — | Email body. |
subject | string | — | Email subject line. Required for new emails; for replies it auto-generates 'Re: ...' when omitted. |
attachments | array | — | Array of integer file IDs to attach. |
recipient_email | string | — | Recipient email address (e.g. 'john@example.com'). Provide to start a new email thread; OMIT to reply in the current email thread. |
Parameters from the server's own tool schema.
Why messages_send_email is rated Medium
This tool creates and sends email messages, which is a reversible write operation. Severity is high because an AI agent with unrestricted access could send emails to arbitrary recipients with arbitrary content, potentially impersonating the user, committing fraud, spamming, or causing reputational harm.
From the tool's definition Tool description states 'Compose and send an email' with ability to add 'subject, CC/BCC, and attachments.' The verb 'send' indicates creation and transmission of new email data.
Attacks that exploit this kind of access
The rule that runs messages_send_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For messages_send_email, this is the rule to start with:
messages_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 Dialogbrain, apply this rule, and every messages_send_email call is checked against it from then on.
Questions about messages_send_email
Compose and send an email — with subject, CC/BCC, and attachments. Use for email; for chat messages (Telegram/WhatsApp/livechat) use messages.send instead. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
messages_send_email accepts 6 parameters: cc, bcc, text, subject, attachments, recipient_email. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for messages_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 Dialogbrain. Nothing to install.
messages_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 messages_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 messages_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.
messages_send_email is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue