verify_email
Verify whether an email address is valid and deliverable. Use this to validate user-provided email addresses during sign-up, form submission, or contact list cleaning. Checks syntax, domain validity, and whether the address is from a disposable email provider. Parameters: email — The email addres...
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/verify-email.md
What verify_email does on X402 Middleware
AI agents call verify_email to retrieve information from X402 Middleware 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 |
|---|---|---|---|
email | string | Yes |
Parameters from the server's own tool schema.
Why verify_email is rated Low
This tool retrieves validation information about an email address without creating, modifying, deleting, or executing operations. It is a read-only check that returns validation status. No data is altered, no code is executed, and no financial transactions occur. The low severity reflects minimal blast radius—incorrect email validation results may cause inconvenience but cannot directly compromise systems or data.
From the tool's definition Tool description states it 'Verify[s] whether an email address is valid and deliverable' by checking 'syntax, domain validity, and whether the address is from a disposable email provider.' These are query/validation operations with no side effects.
Attacks that exploit this kind of access
The rule that runs verify_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_email, this is the rule to start with:
verify_email is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect X402 Middleware, apply this rule, and every verify_email call is checked against it from then on.
Questions about verify_email
Verify whether an email address is valid and deliverable. Use this to validate user-provided email addresses during sign-up, form submission, or contact list cleaning. Checks syntax, domain validity, and whether the address is from a disposable email provider. Parameters: email — The email address to verify (required). It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
verify_email accepts 1 parameter: email. Required: email. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for verify_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 X402 Middleware. Nothing to install.
verify_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 verify_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 verify_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.
verify_email is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue