AI agents call dnssec_validate to retrieve information from Idig Dns without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic and validation tool that queries and analyzes DNSSEC records to assess their security status. It retrieves information and provides analysis with no side effects, data modification, or external execution capability. The tool is purely informational, making it a Read operation with low severity and high confidence.
From the tool's definition Tool 'dnssec_validate' performs validation of DNSSEC chain of trust and returns status values (secure/insecure/bogus/indeterminate). It only checks and reports on existing DNS security configurations without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Validate DNSSEC chain of trust. Returns: secure / insecure / bogus / indeterminate. It is categorised as a Read tool in the Idig Dns MCP Server, which means it retrieves data without modifying state.
Register the Idig Dns MCP server in PolicyLayer and add a rule for dnssec_validate: 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 Idig Dns. Nothing to install.
dnssec_validate 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 dnssec_validate 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 dnssec_validate. 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.
dnssec_validate is provided by the Idig Dns MCP server (https://mcp.softricks.net/sse). 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 →