AI agents use send_email to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.
This tool creates and sends email messages, which is a reversible write operation (emails can be recalled or deleted in most systems, though this depends on provider and timing).
From the tool's definition Tool is named 'send_email' and the server description states it 'enables AI to fully manage email accounts, supporting sending emails with attachments and multiple recipients.' The Chinese description '发送邮件' translates to 'send email,' confirming the…
Documented attack patterns abuse exactly the kind of access send_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Email MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_email:
{
"version": "1",
"default": "deny",
"tools": {
"send_email": {
"limits": [
{
"counter": "send_email_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_email stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
发送邮件. It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP Server 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 Email MCP Server. 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 Email MCP Server MCP server (timecyber/email-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Email MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Email MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.