email_domain_health_check

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 41 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/email-domain-health-check.md

WHAT IT DOES

What email_domain_health_check does on Mcp Knowledge

AI agents call email_domain_health_check to retrieve information from Mcp Knowledge 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
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`email`	string	—	Full email address for additional checks: format validity, role-based detection (e.g. "ceo@stripe.com").
`checks`	array	—	Subset of checks to run. Defaults to all 8: ["mx","spf","dkim","dmarc","blacklist","whois","tls","reputation"]. Use a subset for faster responses (e.g. ["mx","s
`domain`	string	Yes	Domain to check (e.g. "stripe.com" or "@stripe.com"). If an email address is provided here, the domain is extracted automatically.

Parameters from the server's own tool schema.

RISK

Why email_domain_health_check is rated Low

This tool retrieves and analyzes publicly available email domain infrastructure data (DNS records, TLS certificates, WHOIS info, blacklist status) without modifying any systems or data. It is purely informational—aggregating reputation scores and generating signals based on existing records. No side effects, no modifications, no code execution.

From the tool's definition Tool performs 'comprehensive email domain health check' with queries to MX records, SPF authentication, DKIM signing, DMARC policy, DNSBL blacklist status, TLS certificate validity, and WHOIS registration age.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_domain_health_check safely

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

email_domain_health_check Allowed

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

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

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

FAQ

Questions about email_domain_health_check

What does the email_domain_health_check tool do? +

Comprehensive email domain health check: MX routing, SPF authentication, DKIM signing, DMARC policy enforcement, DNSBL blacklist status (Spamhaus/SpamCop/Barracuda), TLS certificate validity, and WHOIS registration age. Aggregates a reputation score 0-100 and generates P0/P1/P2 deliverability signals. Accepts a domain (stripe.com) or email address (info@stripe.com). Detects role-based addresses (info@, support@, admin@, noreply@) that have higher bounce rates. Detects email provider (Google Workspace, Microsoft 365, Amazon SES, etc.). P0 signals: blacklisted / no MX / TLS expired / no SPF + DMARC none. P1 signals: SPF soft-fail / no DKIM selector / DMARC no reporting. P2 signals: role-based address / TLS expires <30d / domain age <90 days. All checks are keyless (no API keys required). Cache TTL 1h. SLA <=10s p95. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does email_domain_health_check accept? +

email_domain_health_check accepts 4 parameters: async, email, checks, 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 email_domain_health_check? +

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

What risk level is email_domain_health_check? +

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

Can I rate-limit email_domain_health_check? +

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

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

email_domain_health_check is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

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