dnssec_check

Check DNSSEC status for a domain: whether DNSKEY records are published, RRSIG signatures are present on A records, and the DS (Delegation Signer) record exists in the parent zone. Returns key algorithm, key tag, and whether validation appears correct. nameserver: optional custom resolver IP.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/dnssec-check.md

WHAT IT DOES

What dnssec_check does on Mcp Nettools

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

RISK

Why dnssec_check is rated Low

This is a pure read operation that queries DNS records and cryptographic signatures to validate DNSSEC configuration. It retrieves and analyzes existing public DNS data without creating, modifying, deleting, or executing any operations. The optional 'nameserver' parameter specifies the resolver but does not change the query's nature as a lookup.

From the tool's definition Tool performs DNS queries and validation checks only: 'Check DNSSEC status for a domain', 'whether DNSKEY records are published', 'RRSIG signatures are present', 'DS (Delegation Signer) record exists'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dnssec_check safely

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

dnssec_check Allowed

dnssec_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": {
    "dnssec_check": {}
  }
}

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

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

FAQ

Questions about dnssec_check

What does the dnssec_check tool do? +

How do I enforce a policy on dnssec_check? +

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

What risk level is dnssec_check? +

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

Can I rate-limit dnssec_check? +

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

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

dnssec_check is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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