Send a single transactional email. Requires Authorization: Bearer <api_key>. Provide either body_html, body_text, or both (Resend will pick the best variant per recipient). All emails ship from RESEND_FROM_ADDRESS — operator must verify that domain in Resend before sending. Returns the provider-a...
AI agents use iliad_transactional_email to create or update resources in AXIS iliad — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AXIS iliad environment.
This tool creates and sends email messages, which are reversible writes rather than destructive actions. While email delivery is observable and has external consequences, emails can theoretically be unsent before reading (via provider APIs) and the action itself is not irreversible in the strictest sense.
From the tool's definition Tool sends transactional email with parameters (recipients, subject, body_html, body_text). Description states 'Send a single transactional email' and 'Returns the provider-assigned message_id plus the accepted recipient list', indicating successful…
Attacks that exploit this kind of access
Send a single transactional email. Requires Authorization: Bearer <api_key>. Provide either body_html, body_text, or both (Resend will pick the best variant per recipient). All emails ship from RESEND_FROM_ADDRESS — operator must verify that domain in Resend before sending. Returns the provider-assigned message_id plus the accepted recipient list. Returns a structured _not_configured envelope when RESEND_API_KEY or RESEND_FROM_ADDRESS is missing. Recipients capped at 50 per call; subject capped at 998 chars; bodies capped at 1 MB. Engineer mode (X-Agent-Mode: engineer — Deliverability, $0.50): instead of sending, pass a. It is categorised as a Write tool in the AXIS iliad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AXIS iliad MCP server in PolicyLayer and add a rule for iliad_transactional_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 AXIS iliad. Nothing to install.
iliad_transactional_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 iliad_transactional_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 iliad_transactional_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.
iliad_transactional_email is provided by the AXIS iliad MCP server (lastmanupinc-hub/axis-iliad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →