check_dns

Resolve all DNS records (A, AAAA, MX, NS, CNAME, TXT, SOA) and check for

Server SiteHealth MCP sitehealth-mcp
Category Read
Risk class Low
Parameters 00 required

What check_dns does on SiteHealth MCP

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

Why check_dns needs a policy

This tool performs DNS lookups and validation—purely informational queries about DNS configuration. It retrieves data about existing DNS records without modifying them, executing code, or triggering side effects. This is a classic Read operation suitable for security auditing and diagnostics.

From the tool's definition Tool resolves DNS records (A, AAAA, MX, NS, CNAME, TXT, SOA) and checks them. 'Resolve' and 'check' indicate read-only queries with no modification or execution of external operations.

Questions about check_dns

What does the check_dns tool do? +

Resolve all DNS records (A, AAAA, MX, NS, CNAME, TXT, SOA) and check for. It is categorised as a Read tool in the SiteHealth MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_dns? +

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

What risk level is check_dns? +

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

Can I rate-limit check_dns? +

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

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

check_dns is provided by the SiteHealth MCP server (sitehealth-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.