New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

setup_domain

Configure DNS records (SPF, DKIM, DMARC) for an email sending domain. Required before sending emails from the domain. Enterprise only.

SERVERStarfield SOURCE@adrata/starfield-mcp
Medium RISK CLASS
Category Write
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/setup-domain.md

What setup_domain does on Starfield

AI agents use setup_domain to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.

ParameterTypeRequiredDescription
domain string Yes Domain name to configure (e.g. "outreach-acme.com")

Parameters from the server's own tool schema.

Why setup_domain is rated Medium

An AI agent can call setup_domain faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.

Questions about setup_domain

What does the setup_domain tool do? +

Configure DNS records (SPF, DKIM, DMARC) for an email sending domain. Required before sending emails from the domain. Enterprise only. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does setup_domain accept? +

setup_domain accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on setup_domain? +

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

What risk level is setup_domain? +

setup_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_domain? +

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

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

setup_domain is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Starfield, and thousands of servers like it.

Across the catalogue

// 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 Starfield'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.