This record as markdown: /tools/io-github-kivanccakmak-yaver/domain-dns-check.md
What domain_dns_check does on Yaver
AI agents call domain_dns_check 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 |
|---|---|---|---|
domain | string | Yes |
Parameters from the server's own tool schema.
Why domain_dns_check is rated Low
This tool performs DNS record verification, which is a read-only operation that queries DNS data to check correctness. It retrieves information and performs validation but does not create, modify, delete, or execute any actions that change system state or have side effects.
From the tool's definition Tool name 'domain_dns_check' and description 'Verify DNS records are correct for a domain' indicate a query/inspection operation that retrieves and validates existing DNS configuration data without modifying it.
Attacks that exploit this kind of access
The rule that runs domain_dns_check 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 domain_dns_check, this is the rule to start with:
domain_dns_check 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 domain_dns_check call is checked against it from then on.
Questions about domain_dns_check
Verify DNS records are correct for a domain. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
domain_dns_check accepts 1 parameter: domain. Required: domain. 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 domain_dns_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 Yaver. Nothing to install.
domain_dns_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 domain_dns_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 domain_dns_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.
domain_dns_check 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