dns_flush

Remove all yaver-managed DNS entries and flush DNS cache.

SERVERYaver SOURCEyaver-cli

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/dns-flush.md

WHAT IT DOES

What dns_flush does on Yaver

AI agents call dns_flush to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why dns_flush is rated Critical

This tool irreversibly deletes DNS entries managed by Yaver and clears the DNS cache. These actions cannot be easily undone and could break network connectivity or service resolution for the entire development environment.

From the tool's definition Tool description states 'Remove all yaver-managed DNS entries and flush DNS cache' — 'Remove all' and 'flush' are explicit destructive operations that irreversibly delete DNS configuration data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dns_flush Hidden

dns_flush is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "dns_flush"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about dns_flush

What does the dns_flush tool do? +

Remove all yaver-managed DNS entries and flush DNS cache. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on dns_flush? +

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

dns_flush is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit dns_flush? +

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

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

dns_flush 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 → Critical-risk tools on this server →

Across the catalogue

delete_dns_record on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →