dns_localname_status

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-localname-status.md

WHAT IT DOES

What dns_localname_status does on Yaver

AI agents call dns_localname_status 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_localname_status is rated Low

Retrieves DNS resolution status and hostname information without modifying system state or data.

From the tool's definition Report this machine's mDNS .local LAN name, Read-only, no root needed.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dns_localname_status Allowed

dns_localname_status 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_localname_status": {}
  }
}

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_localname_status call is checked against it from then on.

FAQ

Questions about dns_localname_status

What does the dns_localname_status tool do? +

Report this machine's mDNS .local LAN name (macOS LocalHostName / Linux hostname) and — the fact that matters — whether <name>.local ACTUALLY resolves on a LAN interface right now (loopback-only is a false green: set but invisible to other devices). Also reports ComputerName, the yaver-managed name if one was set, avahi state on Linux, and a named note when the LAN cannot see the name. Read-only, no root needed. 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_localname_status? +

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

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

Can I rate-limit dns_localname_status? +

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

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

dns_localname_status 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

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

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