Send an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.
AI agents invoke send-email to trigger actions in Mcp Mailtrap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending email is an external operation with real-world side effects — messages are delivered to recipients and cannot be unsent. It triggers outbound communication that may contain sensitive content, spam, or phishing material if misused. The ability to target multiple recipients amplifies the blast radius, making this a high-severity Execute action.
From the tool's definition "Send an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once."
Attacks that exploit this kind of access
Send an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once. It is categorised as a Execute tool in the Mcp Mailtrap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for 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 Mcp Mailtrap. Nothing to install.
send-email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
send-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 →