Check if a domain has DNS records configured (basic availability check)
AI agents call check_domain_availability to retrieve information from DNS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the presence of DNS records for a domain, which is a non-destructive information retrieval operation. It has minimal blast radius even if misused by an AI agent, as it cannot modify infrastructure, execute code, or cause financial harm. The confidence is high because the description clearly indicates a passive lookup operation.
From the tool's definition The tool performs a 'basic availability check' by checking 'if a domain has DNS records configured' — this is a read-only query operation that retrieves DNS information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check if a domain has DNS records configured (basic availability check). It is categorised as a Read tool in the DNS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DNS MCP Server MCP server in PolicyLayer and add a rule for check_domain_availability: 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 DNS MCP Server. Nothing to install.
check_domain_availability is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_domain_availability 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.
Set action: deny in the PolicyLayer policy for check_domain_availability. 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.
check_domain_availability is provided by the DNS MCP Server MCP server (stanibaj/dns-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →