This record as markdown: /tools/io-github-kivanccakmak-yaver/du.md
What du does on Yaver
AI agents call du 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 | — | |
depth | integer | — | Max depth (default: 1) |
Parameters from the server's own tool schema.
Why du is rated Low
This is a read-only diagnostic tool that queries filesystem metadata to display storage consumption. It has no side effects, cannot modify data, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could only gather information about local storage, which is low-risk in a development context.
From the tool's definition Tool named 'du' with description 'Show directory disk usage' — a standard Unix utility that retrieves and reports disk usage statistics without modifying or executing operations.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs du 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 du, this is the rule to start with:
du 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 du call is checked against it from then on.
Questions about du
Show directory disk usage. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
du accepts 2 parameters: path, depth. 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 du: 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.
du 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 du 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 du. 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.
du 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