This record as markdown: /tools/io-github-kivanccakmak-yaver/load-average.md
What load_average does on Yaver
AI agents call load_average 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 load_average is rated Low
This tool only retrieves and displays system performance information (load average and CPU count). It performs no modifications, deletions, code execution, or financial operations. The sole effect is to report existing system data, which is characteristic of a Read operation with minimal risk.
From the tool's definition Tool name 'load_average' and description 'Show system load average and CPU count' indicate a query operation that retrieves system metrics without modifying state.
Attacks that exploit this kind of access
The rule that runs load_average 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 load_average, this is the rule to start with:
load_average 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 load_average call is checked against it from then on.
Questions about load_average
Show system load average and CPU count. 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 load_average: 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.
load_average 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 load_average 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 load_average. 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.
load_average 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