email_domain_register
Register a custom email sending domain for an organization via Resend. Returns DNS records that must be configured in the domain provider before verification. Replaces any previously configured domain. After adding DNS records, call email_domain_verify to check status.
This record as markdown: /tools/com-servicialo-mcp-server/email-domain-register.md
What email_domain_register does on Servicialo
AI agents use email_domain_register to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
domain | string | Yes | |
orgSlug | string | Yes |
Parameters from the server's own tool schema.
Why email_domain_register is rated Medium
This tool modifies organization email infrastructure by registering a domain and replacing prior configurations. While registration is reversible (a new domain can be registered), the replacement of existing domain settings could disrupt email delivery if misapplied.
From the tool's definition Tool description states it 'Register[s] a custom email sending domain' and 'Replaces any previously configured domain.' The 'Replaces' language indicates modification of existing configuration state.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs email_domain_register 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_register, this is the rule to start with:
email_domain_register stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every email_domain_register call is checked against it from then on.
Questions about email_domain_register
Register a custom email sending domain for an organization via Resend. Returns DNS records that must be configured in the domain provider before verification. Replaces any previously configured domain. After adding DNS records, call email_domain_verify to check status. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
email_domain_register accepts 3 parameters: apiKey, domain, orgSlug. Required: domain, orgSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for email_domain_register: 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.
email_domain_register is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the email_domain_register 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 email_domain_register. 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.
email_domain_register 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.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue