This record as markdown: /tools/io-github-kivanccakmak-yaver/disk-usage.md
What disk_usage does on Yaver
AI agents call disk_usage 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | — | Path to check (default: /) |
Parameters from the server's own tool schema.
Why disk_usage is rated Low
This tool only reads and displays disk usage statistics. It has no side effects, cannot modify data, and poses minimal risk even if misused by an agent—at worst, it returns storage information already visible to the system. It clearly falls under the Read category.
From the tool's definition Tool name 'disk_usage' and description 'Show disk usage' indicate a query operation that retrieves system information without modifying, deleting, or executing anything.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs disk_usage 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 disk_usage, this is the rule to start with:
disk_usage 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 disk_usage call is checked against it from then on.
Questions about disk_usage
Show disk usage. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
disk_usage accepts 1 parameter: path. 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 disk_usage: 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.
disk_usage 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 disk_usage 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 disk_usage. 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.
disk_usage 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