send_email
AI agents use send_email to create or update resources in MCP Playground — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Playground environment.
The tool name and server description strongly imply this tool sends emails via Mailtrap, which is an outbound communication action. Sending emails is a Write/Execute-class operation with real-world side effects (external communication). However, since Mailtrap is a mail-testing service (not a live mail delivery service), blast radius may be somewhat limited. The description is empty, so confidence is reduced.
From the tool's definition Tool name is 'send_email'; server description mentions 'sending emails via Mailtrap'
Attacks that exploit this kind of access
send_email. It is categorised as a Write tool in the MCP Playground MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Playground 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 Playground. Nothing to install.
send_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_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 Playground MCP server (jaanlavaerts/mcp_playground). 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 →