disk_manage
Manage disk space safely (allowlist-only reclaim of known-regenerable artifacts: go-build cache, opencode /tmp runtime files, superseded agent versions, and stale Yaver/browser render temp roots (including Playwright profiles, Playwright artifacts, and Chromedp runners). scan = read-only inventor...
This record as markdown: /tools/io-github-kivanccakmak-yaver/disk-manage.md
What disk_manage does on Yaver
AI agents call disk_manage to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | — | Filesystem path to check (default: /) |
action | string | Yes | scan (read-only) | clear (explicit classes, dryRun-first) | sweep (threshold-gated) |
dryRun | boolean | — | clear: preview without deleting (default true). sweep: default false (threshold crossing is the opt-in). |
classes | array | — | Classes to clear (clear only): opencode-tmp-so, yaver-old-agents, yaver-tmp-dirs, go-build-cache |
minAgeMinutes | integer | — | Only consider artifacts idle for at least this long (default 60) |
thresholdPercent | integer | — | sweep: used-percent at/above which deletion is allowed (default 85) |
Parameters from the server's own tool schema.
Why disk_manage is rated Critical
Tool can irreversibly delete cached artifacts and temp files when dryRun is false.
From the tool's definition clear = delete the named classes, dryRun:false to actually delete
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs disk_manage 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_manage, this is the rule to start with:
disk_manage is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every disk_manage call is checked against it from then on.
Questions about disk_manage
Manage disk space safely (allowlist-only reclaim of known-regenerable artifacts: go-build cache, opencode /tmp runtime files, superseded agent versions, and stale Yaver/browser render temp roots (including Playwright profiles, Playwright artifacts, and Chromedp runners). scan = read-only inventory of what is reclaimable. clear = delete the named classes (dryRun defaults to true — pass dryRun:false to actually delete). sweep = threshold-gated clear (only acts at/above the used-percent threshold, default 85). Never touches secrets, keys, git work trees, or anything outside the allowlist. This is the fix for 'no space left on device' mid-build — the deploy preflight now fails fast naming this tool as the route to fix. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
disk_manage accepts 6 parameters: path, action, dryRun, classes, minAgeMinutes, thresholdPercent. Required: action. 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_manage: 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_manage is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the disk_manage 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_manage. 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_manage 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.
Across the catalogue