ghl_verify_email_domain

Trigger DNS verification check for an email sending domain. Returns whether DKIM, SPF, and DMARC records are correctly configured.

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/ghl-verify-email-domain.md

What ghl_verify_email_domain does on GoHighLevel MCP Server

AI agents invoke ghl_verify_email_domain to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why ghl_verify_email_domain is rated High

The tool triggers an active DNS verification check against external DNS infrastructure, making it an Execute category action. While it returns read-like information (DKIM/SPF/DMARC configuration status), the 'trigger' language indicates it initiates an external operation. The blast radius is low since it only performs a verification check with no data modification or deletion possible.

From the tool's definition 'Trigger DNS verification check' — actively triggers an external operation (DNS lookup/verification process) rather than simply reading stored data

Questions about ghl_verify_email_domain

What does the ghl_verify_email_domain tool do? +

Trigger DNS verification check for an email sending domain. Returns whether DKIM, SPF, and DMARC records are correctly configured. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ghl_verify_email_domain? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_verify_email_domain: 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 ghl_verify_email_domain? +

ghl_verify_email_domain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ghl_verify_email_domain? +

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

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

ghl_verify_email_domain is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, 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 GoHighLevel MCP Server'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.