AI agents call dane_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.
DANE/TLSA validation is a diagnostic check that queries and compares DNS records and TLS certificates. It retrieves and analyzes existing data without creating, modifying, deleting, or executing arbitrary operations. This is consistent with the other sibling tools on this DNS diagnostics server (dns_lookup, dnssec_validate, mx_check, etc.), which are all Read-category tools.
From the tool's definition Tool description states it 'cross-validates TLSA DNS records against the live TLS certificate' - a validation and diagnostic operation with no data modification, deletion, or external state changes.
Attacks that exploit this kind of access
DANE/TLSA validation: cross-validates TLSA DNS records against the live TLS certificate. Supports all four TLSA usage types. 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 dane_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.
dane_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 dane_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 dane_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.
dane_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 →