// SCAN REPORT

X402mail

4 tools. 1 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 30/06/2026

How to control X402mail ↓

TOOL MAP

What X402mail exposes to your agents

Read (3) Write / Execute (0) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous X402mail tools

Financial · Critical send_email The server description explicitly states that emails are sent with USDC micropayments.

1 of X402mail's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control X402mail

PolicyLayer is an MCP gateway — it sits between your AI agents and X402mail, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "send_email": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations

{
  "get_inbox": {
    "limits": [
      {
        "counter": "get_inbox_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register X402mail — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON X402MAIL →

Instant setup, no code required.

FULL CATALOGUE

All 4 X402mail tools

FINANCIAL 1 tools

Financial send_email send_email

READ 3 tools

Read get_inbox Get your inbox address and message counts. Costs ~$0.001 in USDC. Read list_messages List inbox messages. Costs ~$0.002 in USDC. Read read_message Read a specific message by ID. Marks it as read. Costs ~$0.001 in USDC.

FAQ

Questions about X402mail

Can an AI agent move money through the X402mail MCP server? +

Yes. The X402mail server exposes 1 financial tools including send_email. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the X402mail MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on X402mail? +

Register the X402mail MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every X402mail tool call.

Deterministic rules across all 4 X402mail tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON X402MAIL →

Instant setup, no code required.

4 X402mail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.