verify_emails

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/verify-emails.md

WHAT IT DOES

What verify_emails does on Max MCP Server

AI agents use verify_emails to commit financial operations through Max MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why verify_emails is rated Critical

Tool consumes financial credits for email verification, constituting a financial obligation.

From the tool's definition CHARGES CREDITS (402 if insufficient)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_emails safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_emails, this is the rule to start with:

verify_emails Approval-gated

Any call to verify_emails is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_emails": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every verify_emails call is checked against it from then on.

FAQ

Questions about verify_emails

What does the verify_emails tool do? +

Queue email verification (Bouncer) for prospect_ids or a whole list_id. CHARGES CREDITS (402 if insufficient). Async: returns 202 {job_id, job_ids, total}; a cron writes deliverable/risky/undeliverable/unknown onto each prospect. It is categorised as a Financial tool in the Max MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on verify_emails? +

Register the Max MCP Server MCP server in PolicyLayer and add a rule for verify_emails: 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 Max MCP Server. Nothing to install.

What risk level is verify_emails? +

verify_emails is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit verify_emails? +

Yes. Add a rate_limit block to the verify_emails 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 verify_emails completely? +

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

verify_emails is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Max MCP Server, and thousands of servers like it.

This server

All 415 Max MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →