verify_email

Verify email address deliverability and get risk assessment. Charges will be deducted from the specified location wallet.

SERVERGoHighLevel MCP Server SOURCEhooker-dev/hailey-mcp

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/hooker-dev-hailey-mcp/verify-email.md

WHAT IT DOES

What verify_email does on GoHighLevel MCP Server

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

RISK

Why verify_email is rated Critical

Although the primary action is verifying an email address (a Read/Execute operation), the tool explicitly states that it deducts charges from a location wallet, making it a financial transaction. Each invocation consumes funds, so misuse by an AI agent could result in unintended financial costs at scale.

From the tool's definition Charges will be deducted from the specified location wallet

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_email safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, 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 Approval-gated

Any call to verify_email 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_email": {
      "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 GoHighLevel MCP Server, apply this rule, and every verify_email call is checked against it from then on.

FAQ

Questions about verify_email

What does the verify_email tool do? +

Verify email address deliverability and get risk assessment. Charges will be deducted from the specified location wallet. It is categorised as a Financial tool in the GoHighLevel 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_email? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is verify_email? +

verify_email 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_email? +

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.

How do I block verify_email completely? +

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.

What MCP server provides verify_email? +

verify_email is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 255 GoHighLevel 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 →