Verify email address deliverability and get risk assessment. Charges will be deducted from the specified location wallet.
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.
Although the primary action is verifying an email address (a Read-like operation), the tool explicitly states that charges are deducted from a location wallet upon use. This makes it a Financial category tool, as each invocation commits a financial obligation. Misuse by an AI agent (e.g., bulk verification runs) could rapidly drain wallet funds, warranting high severity.
From the tool's definition Charges will be deducted from the specified location wallet
Attacks that exploit this kind of access
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.
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.
verify_email is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →