Send an email via POST /mail/send. Supply at least one
AI agents use send_mail to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates new email records and sends communications, which is a reversible write operation. While email sending has side effects (outbound communication), it does not destroy data, execute arbitrary code, or move funds. The severity is medium because misuse could result in spam, phishing, or reputational harm, but the action is not inherently destructive.
From the tool's definition Tool name 'send_mail' combined with description 'Send an email via POST /mail/send' indicates the tool creates and sends email messages, which are data modifications.
Documented attack patterns abuse exactly the kind of access send_mail gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for send_mail:
{
"version": "1",
"default": "deny",
"tools": {
"send_mail": {
"limits": [
{
"counter": "send_mail_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} send_mail 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.
Send an email via POST /mail/send. Supply at least one. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for send_mail: 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 Ap2. Nothing to install.
send_mail 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_mail 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_mail. 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_mail is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.