verify_email

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

SERVERGhl SOURCEghl-mcp-server
Critical RISK CLASS
Category Financial
Parameters 33 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/verify-email.md

What verify_email does on Ghl

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

ParameterTypeRequiredDescription
type string Yes Verification type: "email" for direct email verification, "contact" for contact ID verification
verify string Yes Email address to verify (if type=email) or contact ID (if type=contact)
locationId string Yes Location ID - charges will be deducted from this location wallet

Parameters from the server's own tool schema.

Why verify_email is rated Critical

The tool explicitly states it deducts charges from a location wallet, meaning each invocation incurs a financial cost. This makes it a Financial category tool. Misuse (e.g., bulk verification of many addresses) could result in significant unexpected charges.

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

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 Ghl MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does verify_email accept? +

verify_email accepts 3 parameters: type, verify, locationId. Required: type, verify, locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on verify_email? +

Register the Ghl 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 Ghl. 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 Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ghl, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.