email_domain_verify

SERVERServicialo SOURCE@servicialo/mcp-server

High RISK CLASS

Category Execute

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/email-domain-verify.md

WHAT IT DOES

What email_domain_verify does on Servicialo

AI agents invoke email_domain_verify to trigger actions in Servicialo. 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.

Parameter	Type	Required	Description
`apiKey`	string	—
`orgSlug`	string	Yes

Parameters from the server's own tool schema.

RISK

Why email_domain_verify is rated High

This tool initiates an external process (DNS verification check) rather than simply reading data. It performs an action against an external DNS system and returns a status, making it Execute. The blast radius is medium: misuse could cause confusion or repeated verification attempts, but it doesn't modify data or incur financial consequences.

From the tool's definition 'Trigger DNS verification for the configured email domain' — the tool actively triggers an external DNS verification operation whose outcome depends on DNS propagation state

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_domain_verify safely

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

email_domain_verify Rate-limited

email_domain_verify stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "email_domain_verify": {
      "limits": [
        {
          "counter": "email_domain_verify_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about email_domain_verify

What does the email_domain_verify tool do? +

Trigger DNS verification for the configured email domain and return updated status. Call this after the organization has added the required DNS records. Status will be VERIFIED (ready to send), PENDING (DNS not yet propagated), or FAILED. It is categorised as a Execute tool in the Servicialo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does email_domain_verify accept? +

email_domain_verify accepts 2 parameters: apiKey, orgSlug. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on email_domain_verify? +

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

What risk level is email_domain_verify? +

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

Can I rate-limit email_domain_verify? +

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

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

email_domain_verify is provided by the Servicialo MCP server (@servicialo/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 Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools → High-risk tools on this server →

Across the catalogue

disable_modsecurity_domain on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →