email.transactional.send
⚡ ACTION: Send transactional email — plain text or HTML body, multiple recipients, reply-to. Requires verified sender domain. 3,000 free emails/month (Resend)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/email.transactional.send.md
What email.transactional.send does on Apibase
AI agents use email.transactional.send to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | object | Yes | Recipient email address(es) — single email or array of emails |
from | string | — | Sender email (default: noreply@apibase.pro). Must be a verified domain. |
html | string | — | HTML email body (alternative to text) |
text | string | — | Plain text email body |
subject | string | Yes | Email subject line |
reply_to | string | — | Reply-to email address |
Parameters from the server's own tool schema.
Why email.transactional.send is rated Medium
Sends emails (creates/modifies communication data), but is reversible and transactional in nature.
From the tool's definition Send transactional email to multiple recipients; creates persistent side effects.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs email.transactional.send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email.transactional.send, this is the rule to start with:
email.transactional.send 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 Apibase, apply this rule, and every email.transactional.send call is checked against it from then on.
Questions about email.transactional.send
⚡ ACTION: Send transactional email — plain text or HTML body, multiple recipients, reply-to. Requires verified sender domain. 3,000 free emails/month (Resend). It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
email.transactional.send accepts 6 parameters: to, from, html, text, subject, reply_to. Required: to, subject. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for email.transactional.send: 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 Apibase. Nothing to install.
email.transactional.send 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 email.transactional.send 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 email.transactional.send. 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.
email.transactional.send is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue