Check if DNSSEC is enabled for a domain
AI agents call check_dnssec 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 performs a passive DNS security check by querying DNSSEC records and validation status. It retrieves information about domain security configuration without creating, modifying, deleting, or executing operations. The operation has no side effects and is purely informational, consistent with Read category tools like other DNS query operations (query_a_record, query_mx_record, etc.) on this server.
From the tool's definition Tool name 'check_dnssec' and description 'Check if DNSSEC is enabled for a domain' indicate a query operation that retrieves DNSSEC validation status without modifying any data or triggering external actions.
Attacks that exploit this kind of access
Check if DNSSEC is enabled for a domain. 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_dnssec: 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_dnssec 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_dnssec 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_dnssec. 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_dnssec 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 →