email_auth

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/email-auth.md

WHAT IT DOES

What email_auth does on ScorpTech x402 API

AI agents call email_auth to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name, e.g. example.com

Parameters from the server's own tool schema.

RISK

Why email_auth is rated Low

Even though email_auth only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_auth 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_auth, this is the rule to start with:

email_auth Allowed

email_auth is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "email_auth": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every email_auth call is checked against it from then on.

FAQ

Questions about email_auth

What does the email_auth tool do? +

Email authentication & deliverability posture for a domain: SPF (qualifier, lookup count, duplicates), DMARC policy/rua/pct, DKIM probe across common selectors, MTA-STS, TLS-RPT, BIMI, MX; scored with actionable issues. Useful for spoofing-risk and vendor checks. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/email-auth. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.

What parameters does email_auth accept? +

email_auth accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on email_auth? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for email_auth: 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.

What risk level is email_auth? +

email_auth is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit email_auth? +

Yes. Add a rate_limit block to the email_auth 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.

How do I block email_auth completely? +

Set action: deny in the PolicyLayer policy for email_auth. 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.

What MCP server provides email_auth? +

email_auth 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.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →