Send a batch of bulk emails (Mailtrap bulk-stream API) in one call. Shared fields go on
AI agents use batch-send-bulk-email to create or update resources in Mcp Mailtrap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mailtrap environment.
The tool creates and sends email messages in bulk, which is a reversible write operation that modifies system state (creates new sent emails). While emails cannot be unsent once delivered, the tool itself permits bulk creation of messages.
From the tool's definition Tool performs 'batch-send-bulk-email' which creates and sends multiple email messages. Description states it sends emails via Mailtrap's bulk-stream API.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Send a batch of bulk emails (Mailtrap bulk-stream API) in one call. Shared fields go on. It is categorised as a Write tool in the Mcp Mailtrap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for batch-send-bulk-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 Mcp Mailtrap. Nothing to install.
batch-send-bulk-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 batch-send-bulk-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 batch-send-bulk-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.
batch-send-bulk-email is provided by the Mcp Mailtrap MCP server (mcp-mailtrap). 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 →