Retrieve full details of a specific sent transactional email by ID, including HTML and plain text content.
AI agents call get-email 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 performs a data retrieval operation on historical email records. While email content may be sensitive, the action itself is a passive query that does not modify state, execute code, trigger external operations, or commit financial transactions. The low severity reflects that misuse would primarily result in information disclosure rather than system compromise or irreversible data loss.
From the tool's definition Tool description explicitly states 'Retrieve full details of a specific sent transactional email by ID'. The verb 'Retrieve' and the clarification that it accesses existing sent email records (not creating, modifying, deleting, or executing operations)…
Documented attack patterns abuse exactly the kind of access get-email 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 get-email:
{
"version": "1",
"default": "deny",
"tools": {
"get-email": {}
}
}get-email 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.
Retrieve full details of a specific sent transactional email by ID, including HTML and plain text content. 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 get-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 Sending MCP. Nothing to install.
get-email 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 get-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 get-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.
get-email 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.