email_parse
Parse a raw email (.eml / RFC 5322 + MIME) for triage: decoded headers (RFC 2047), addresses, Received hop chain with relays, IPs, timestamps and delays, originating IP, Authentication-Results (SPF / DKIM / DMARC / ARC), DKIM-Signature domains and selectors, MIME part tree, attachments (name, typ...
This record as markdown: /tools/com-it-scorptech-x402/email-parse.md
What email_parse does on ScorpTech x402 API
AI agents invoke email_parse to trigger actions in ScorpTech x402 API. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
raw | string | Yes | Full raw message source including headers |
maxBodyChars | integer | — |
Parameters from the server's own tool schema.
Why email_parse is rated High
email_parse triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs email_parse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_parse, this is the rule to start with:
email_parse stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every email_parse call is checked against it from then on.
Questions about email_parse
Parse a raw email (.eml / RFC 5322 + MIME) for triage: decoded headers (RFC 2047), addresses, Received hop chain with relays, IPs, timestamps and delays, originating IP, Authentication-Results (SPF / DKIM / DMARC / ARC), DKIM-Signature domains and selectors, MIME part tree, attachments (name, type, size, SHA-256, risky extensions), text body and links (with anchor-text vs href domain mismatch). Adds phishing / spoofing indicators (From vs Return-Path / Reply-To misalignment, display-name spoofing, brand impersonation, auth failures, urgency language) and a 0-100 risk score. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/email-parse. It is categorised as a Execute tool in the ScorpTech x402 API MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
email_parse accepts 2 parameters: raw, maxBodyChars. Required: raw. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for email_parse: 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 ScorpTech x402 API. Nothing to install.
email_parse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the email_parse 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 email_parse. 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.
email_parse is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue