dns_list

List all yaver-managed DNS entries.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 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-list.md

WHAT IT DOES

What dns_list does on Yaver

AI agents call dns_list 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.

RISK

Why dns_list is rated Low

This tool retrieves and lists existing DNS configuration data without modifying, executing, or deleting anything. It is a straightforward read operation. Severity is low because DNS listing reveals infrastructure information but does not directly impact system integrity or enable further unauthorized actions on its own.

From the tool's definition Tool name 'dns_list' and description 'List all yaver-managed DNS entries' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dns_list 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_list, this is the rule to start with:

dns_list Allowed

dns_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every dns_list call is checked against it from then on.

FAQ

Questions about dns_list

What does the dns_list tool do? +

List all yaver-managed DNS entries. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dns_list? +

Register the Yaver MCP server in PolicyLayer and add a rule for dns_list: 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_list? +

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

Can I rate-limit dns_list? +

Yes. Add a rate_limit block to the dns_list 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_list completely? +

Set action: deny in the PolicyLayer policy for dns_list. 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_list? +

dns_list 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →