Purpose: List recently sent emails (transactional emails sent via send-email) with metadata: recipient, subject, status, timestamps. NOT for: Listing broadcast campaigns (use list-broadcasts). Not for composing or sending. Returns: Paginated list with to, subject, status, created_at, and ID per e...
AI agents call list-emails to retrieve information from Email Sending MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing email data with no side effects. It does not create, modify, delete, or execute any operations—only fetches metadata about previously sent emails. This is a pure read operation with minimal blast radius if misused; an AI agent could only extract information about emails that have already been sent.
From the tool's definition Tool description explicitly states it 'List recently sent emails' and 'Returns: Paginated list with to, subject, status, created_at, and ID per email.' The description clarifies it is 'NOT for...composing or sending,' confirming it only retrieves historical…
Documented attack patterns abuse exactly the kind of access list-emails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list-emails:
{
"version": "1",
"default": "deny",
"tools": {
"list-emails": {}
}
}list-emails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Purpose: List recently sent emails (transactional emails sent via send-email) with metadata: recipient, subject, status, timestamps. NOT for: Listing broadcast campaigns (use list-broadcasts). Not for composing or sending. Returns: Paginated list with to, subject, status, created_at, and ID per email. When to use: - User asks. It is categorised as a Read tool in the Email Sending MCP MCP Server, which means it retrieves data without modifying state.
Register the Email Sending MCP server in PolicyLayer and add a rule for list-emails: 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 Sending MCP. Nothing to install.
list-emails is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-emails 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 list-emails. 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.
list-emails is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.