New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

dns_lookup

DNS lookup for a hostname.

SERVERYaver SOURCEyaver-cli
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about dns_lookup

What does the dns_lookup tool do? +

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.

What parameters does dns_lookup accept? +

dns_lookup accepts 2 parameters: host, type. Required: host. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dns_lookup? +

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.

What risk level is dns_lookup? +

dns_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dns_lookup? +

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.

How do I block dns_lookup completely? +

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.

What MCP server provides dns_lookup? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.