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

domain_check_email_security

Check SPF, DMARC, and DKIM email authentication for a domain. domain: Domain without protocol e.g. "google.com". Returns: overall_grade (A–F), spf_score, dmarc_score, dkim_score (each 0–10), spf_record, dmarc_record, dkim_selectors_found. Scores reflect live DNS via Cloudflare DoH — no cache. SPF...

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server
Low RISK CLASS
Category Read
Parameters 10 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/domain-check-email-security.md

What domain_check_email_security does on DataNexus MCP

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

ParameterTypeRequiredDescription
domain string Domain without protocol e.g. google.com. Required.

Parameters from the server's own tool schema.

Why domain_check_email_security is rated Low

This is a passive reconnaissance tool that queries public DNS information about a domain's email security posture. It retrieves and analyzes existing records without creating, modifying, or deleting any data. The function performs DNS lookups and scoring calculations on read-only public infrastructure.

From the tool's definition Tool queries DNS records via Cloudflare DoH to retrieve email authentication configurations (SPF, DMARC, DKIM). Returns read-only data: grades, scores, and record contents. No modifications, deletions, or side effects.

Questions about domain_check_email_security

What does the domain_check_email_security tool do? +

Check SPF, DMARC, and DKIM email authentication for a domain. domain: Domain without protocol e.g. "google.com". Returns: overall_grade (A–F), spf_score, dmarc_score, dkim_score (each 0–10), spf_record, dmarc_record, dkim_selectors_found. Scores reflect live DNS via Cloudflare DoH — no cache. SPF: -all=10 (strict), ~all=7, ?all=4, none=2, +all=0 (open relay). DMARC: p=reject=10, p=quarantine=7, p=none=4, absent=0; +1 for rua set. DKIM: selector found=10, none=0. Checks 10 common selectors in parallel. Example: check_email_security(domain="google.com"). It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.

What parameters does domain_check_email_security accept? +

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

How do I enforce a policy on domain_check_email_security? +

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

What risk level is domain_check_email_security? +

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

Can I rate-limit domain_check_email_security? +

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

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

domain_check_email_security is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on DataNexus, 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 DataNexus'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.