util_dns_lookup
Resolve A, AAAA, CNAME, MX, TXT, and NS records for fast domain and delivery checks.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-dns-lookup.md
What util_dns_lookup does on Delx MCP Server
AI agents call util_dns_lookup to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain to resolve |
timeout | integer | — | Timeout in seconds (1-15) |
record_type | string | — | DNS record type |
Parameters from the server's own tool schema.
Why util_dns_lookup is rated Low
DNS record resolution is a standard read-only query operation. It retrieves publicly available DNS information with no ability to modify records, execute code, delete data, or commit financial obligations. The low severity reflects minimal risk even if misused by an AI agent, as DNS lookups themselves cause no harm; the information returned is already public.
From the tool's definition Tool description states it 'Resolve[s] A, AAAA, CNAME, MX, TXT, and NS records for fast domain and delivery checks' — a DNS lookup is a purely informational read operation that queries existing DNS records without modification or side effects.
Attacks that exploit this kind of access
The rule that runs util_dns_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_dns_lookup, this is the rule to start with:
util_dns_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every util_dns_lookup call is checked against it from then on.
Questions about util_dns_lookup
Resolve A, AAAA, CNAME, MX, TXT, and NS records for fast domain and delivery checks. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_dns_lookup accepts 3 parameters: domain, timeout, record_type. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_dns_lookup: 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 Delx MCP Server. Nothing to install.
util_dns_lookup 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 util_dns_lookup 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 util_dns_lookup. 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.
util_dns_lookup is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue