verify_domain

Check DNS propagation status for an email domain. Returns verification status for SPF, DKIM, and DMARC records. Enterprise only.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What verify_domain does on Starfield

AI agents call verify_domain to retrieve information from Starfield 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
`domain`	string	Yes	Domain name to verify (e.g. "outreach-acme.com")

Parameters from the server's own tool schema.

RISK

Why verify_domain is rated Low

Even though verify_domain only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_domain safely

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

verify_domain Allowed

verify_domain 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": {
    "verify_domain": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about verify_domain

What does the verify_domain tool do? +

Check DNS propagation status for an email domain. Returns verification status for SPF, DKIM, and DMARC records. Enterprise only. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does verify_domain accept? +

verify_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 verify_domain? +

Register the Starfield MCP server in PolicyLayer and add a rule for verify_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 verify_domain? +

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

Can I rate-limit verify_domain? +

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

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

verify_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.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

The MCP Attack Database →

Guides

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