Send an email in sandbox mode to a test inbox without delivering to your recipients
AI agents use send-sandbox-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.
This tool creates email records in a sandbox environment. While it performs a write operation (creating email data), the sandbox mode and test inbox context limit the blast radius compared to actual email delivery. It's reversible (emails can be deleted), making it Write rather than Execute or Financial.
From the tool's definition Tool description states 'Send an email in sandbox mode to a test inbox' - this is a creation action that modifies data (creates email records) in a reversible manner.
Attacks that exploit this kind of access
Send an email in sandbox mode to a test inbox without delivering to your recipients. 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 send-sandbox-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-sandbox-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 send-sandbox-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-sandbox-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-sandbox-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 →