dns_localname_set
Give this machine a stable mDNS LAN name <name>.local so the web dashboard / agent are reachable by name (yaver.local:18080) from every device on the LAN instead of a raw IP — the same trick as a home router or a Raspberry Pi with avahi. macOS: scutil --set LocalHostName + ComputerName (root via ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/dns-localname-set.md
What dns_localname_set does on Yaver
AI agents use dns_localname_set 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Desired .local name — a single token, no spaces or dots (e.g. "yaver"). The .local suffix is implied. |
Parameters from the server's own tool schema.
Why dns_localname_set is rated Medium
Modifies system DNS configuration reversibly; owner-only protects against unauthorized access.
From the tool's definition set LocalHostName, set-hostname, persists previous name
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs dns_localname_set 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_set, this is the rule to start with:
dns_localname_set 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every dns_localname_set call is checked against it from then on.
Questions about dns_localname_set
Give this machine a stable mDNS LAN name <name>.local so the web dashboard / agent are reachable by name (yaver.local:18080) from every device on the LAN instead of a raw IP — the same trick as a home router or a Raspberry Pi with avahi. macOS: scutil --set LocalHostName + ComputerName (root via YAVER_LOGIN_PASSWORD in ~/.yaver/local-secrets.env). Linux: hostnamectl set-hostname; warns when avahi-daemon is not running (name set but not advertised). Verifies by resolving <name>.local on a LAN interface before returning, and persists the previous name for dns_localname_restore. 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.
dns_localname_set accepts 1 parameter: name. Required: name. 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 dns_localname_set: 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.
dns_localname_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dns_localname_set 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 dns_localname_set. 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.
dns_localname_set 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