Get the raw RFC-822 bytes of an inbound email message, base64-encoded. The decoded bytes are bit-identical to the DKIM-signed original — no parsing, normalization, or CRLF cleanup. Use this for cryptographic verification (DKIM checks, zk-email proofs). Inbound messages only; outbound returns 404....
AI agents call get_email_raw to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns email message data without modification, creation, deletion, or execution. The intended use case is verification/inspection, not agent actions with side effects. The blast radius of misuse is limited to unauthorized email disclosure, a confidentiality risk but not a systemic integrity or financial threat. Classified as Read/low.
From the tool's definition Tool description explicitly states 'Get the raw RFC-822 bytes of an inbound email message, base64-encoded.' The verb is 'Get' (retrieval only).
Attacks that exploit this kind of access
Get the raw RFC-822 bytes of an inbound email message, base64-encoded. The decoded bytes are bit-identical to the DKIM-signed original — no parsing, normalization, or CRLF cleanup. Use this for cryptographic verification (DKIM checks, zk-email proofs). Inbound messages only; outbound returns 404. For display/threading, use get_email instead. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 MCP server in PolicyLayer and add a rule for get_email_raw: 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 Run402. Nothing to install.
get_email_raw 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_raw 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_raw. 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_raw is provided by the Run402 MCP server (kychee-com/run402). 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 →