hostname_info

Show hostname and OS info.

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/hostname-info.md

WHAT IT DOES

What hostname_info does on Yaver

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

This tool queries and displays read-only system metadata (hostname and operating system details). There is no data creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal — an attacker gains only basic system identification information that is often public or easily discoverable through other means.

From the tool's definition Tool description states 'Show hostname and OS info' — retrieves system information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hostname_info Allowed

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

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

FAQ

Questions about hostname_info

What does the hostname_info tool do? +

Show hostname and OS info. 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 hostname_info? +

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

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

Can I rate-limit hostname_info? +

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

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

hostname_info 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 →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

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