email_domain_get

Get the email sending domain configured for an organization and its verification status (PENDING, VERIFIED, FAILED). Returns null if no domain is configured. Use email_domain_register to set one up.

SERVERServicialo SOURCE@servicialo/mcp-server

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What email_domain_get does on Servicialo

AI agents call email_domain_get to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

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

Parameters from the server's own tool schema.

RISK

Why email_domain_get is rated Low

This tool retrieves configuration metadata about an email domain. It performs a read-only query that returns status information (PENDING, VERIFIED, or FAILED) without any side effects. No data is created, modified, deleted, or executed.

From the tool's definition Tool name contains 'get' and description states it 'Get[s] the email sending domain configured for an organization and its verification status'; returns information about existing configuration without modifying, creating, or deleting anything.

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_domain_get 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_get, this is the rule to start with:

email_domain_get Allowed

email_domain_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "email_domain_get": {}
  }
}

ALLOW ONLY 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_get call is checked against it from then on.

FAQ

Questions about email_domain_get

What does the email_domain_get tool do? +

Get the email sending domain configured for an organization and its verification status (PENDING, VERIFIED, FAILED). Returns null if no domain is configured. Use email_domain_register to set one up. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.

What parameters does email_domain_get accept? +

email_domain_get 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_get? +

Register the Servicialo MCP server in PolicyLayer and add a rule for email_domain_get: 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_get? +

email_domain_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit email_domain_get? +

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

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

email_domain_get 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →