AI agents call resolve_check 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 tool performs DNS resolution lookups and returns diagnostic status codes. It only queries and retrieves DNS data with no side effects, modifications, or destructive actions.
From the tool's definition DNS resolution diagnostics. Returns status: ok / nxdomain / nodata / servfail / refused / timeout / degraded.
Attacks that exploit this kind of access
DNS resolution diagnostics. Returns status: ok / nxdomain / nodata / servfail / refused / timeout / degraded. 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 resolve_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 Idig Dns. Nothing to install.
resolve_check 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 resolve_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.
Set action: deny in the PolicyLayer policy for resolve_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.
resolve_check 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 →