This record as markdown: /tools/io-github-kivanccakmak-yaver/dns-lookup.md
What dns_lookup does on Yaver
AI agents call dns_lookup to retrieve information from Yaver 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 |
|---|---|---|---|
host | string | Yes | Hostname to lookup |
type | string | — | Record type: A, AAAA, MX, CNAME, TXT (default: A) |
Parameters from the server's own tool schema.
Why dns_lookup is rated Low
DNS lookup is a standard information retrieval operation that queries the Domain Name System to resolve hostnames to IP addresses. It has no side effects, does not modify data, and does not execute arbitrary code. While DNS lookups can theoretically be chained into reconnaissance for attacks, the tool itself performs only read-only queries. This is a low-severity Read operation typical of network utilities.
From the tool's definition Tool name 'dns_lookup' and description 'DNS lookup for a hostname' indicate a query operation that retrieves DNS records without modifying data or executing code.
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs dns_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_lookup, this is the rule to start with:
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 Yaver, apply this rule, and every dns_lookup call is checked against it from then on.
Questions about dns_lookup
DNS lookup for a hostname. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
dns_lookup accepts 2 parameters: host, type. Required: host. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for 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 Yaver. Nothing to install.
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 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 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.
dns_lookup is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue