This record as markdown: /tools/io-github-kivanccakmak-yaver/uname.md
What uname does on Yaver
AI agents call uname 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.
Why uname is rated Low
This tool queries and retrieves system information (kernel version, architecture, hostname) without modifying, executing commands, or affecting system state. It is a straightforward informational read operation with minimal security impact.
From the tool's definition Tool description: 'Show kernel, architecture, hostname info.' The verb 'show' indicates retrieval of system information with no side effects.
Attacks that exploit this kind of access
The rule that runs uname 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 uname, this is the rule to start with:
uname is read-only, so it stays allowed. 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 uname call is checked against it from then on.
Questions about uname
Show kernel, architecture, hostname info. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for uname: 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.
uname is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the uname 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 uname. 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.
uname 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