dns_localname_restore

Revert a yaver-set mDNS local name back to the LocalHostName/ComputerName recorded before dns_localname_set ran. No-op with a clear message when yaver never set a name. Owner-only.

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What dns_localname_restore does on Yaver

AI agents use dns_localname_restore to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

RISK

Why dns_localname_restore is rated Medium

Reverts DNS name changes reversibly; no data deletion or code execution involved.

From the tool's definition Revert a yaver-set mDNS local name back to previously recorded value

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dns_localname_restore Rate-limited

dns_localname_restore stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_localname_restore": {
      "limits": [
        {
          "counter": "dns_localname_restore_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about dns_localname_restore

What does the dns_localname_restore tool do? +

Revert a yaver-set mDNS local name back to the LocalHostName/ComputerName recorded before dns_localname_set ran. No-op with a clear message when yaver never set a name. Owner-only. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dns_localname_restore? +

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

dns_localname_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dns_localname_restore? +

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

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

dns_localname_restore 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 678 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →