Low Risk

get_disk_usage

Get disk space information

How to control get_disk_usage ↓

What get_disk_usage does on Mcp Wsl Exec

AI agents call get_disk_usage to retrieve information from Mcp Wsl Exec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_disk_usage needs a policy

This tool queries disk space metrics, which is a read-only operation with no side effects. It does not execute commands, modify data, delete files, or trigger external operations. Despite being on a command execution server, this specific tool is limited to retrieving and reporting disk usage statistics.

From the tool's definition Tool name 'get_disk_usage' and description 'Get disk space information' indicate a query operation that retrieves system information without modification or execution of commands.

Documented attack patterns abuse exactly the kind of access get_disk_usage gives an agent:

How to control get_disk_usage

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Wsl Exec, and nothing reaches the server without passing your rules. This is the rule we recommend for get_disk_usage:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_disk_usage": {}
  }
}

get_disk_usage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Wsl Exec — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_disk_usage

What does the get_disk_usage tool do? +

Get disk space information. It is categorised as a Read tool in the Mcp Wsl Exec MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_disk_usage? +

Register the Mcp Wsl Exec MCP server in PolicyLayer and add a rule for get_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 Mcp Wsl Exec. Nothing to install.

What risk level is get_disk_usage? +

get_disk_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_disk_usage? +

Yes. Add a rate_limit block to the get_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.

How do I block get_disk_usage completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_disk_usage? +

get_disk_usage is provided by the Mcp Wsl Exec MCP server (spences10/mcp-wsl-exec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Wsl Exec tool call.

Start from Mcp Wsl Exec, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 Mcp Wsl Exec tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.