storage_get_disk_info

Get detailed disk/partition information including usage and mount points.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aapanel-mcp/storage-get-disk-info.md

WHAT IT DOES

What storage_get_disk_info does on Aapanel

AI agents call storage_get_disk_info to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why storage_get_disk_info is rated Low

This tool retrieves and queries disk/partition information such as usage statistics and mount points. It performs read-only operations with no side effects, reversible modifications, or external state changes. The low severity reflects that disk information disclosure poses minimal risk compared to other categories, though it could inform an attacker about system architecture.

From the tool's definition Tool name includes 'get', and description states 'Get detailed disk/partition information including usage and mount points' with no modification or deletion capability mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs storage_get_disk_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_get_disk_info, this is the rule to start with:

storage_get_disk_info Allowed

storage_get_disk_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "storage_get_disk_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every storage_get_disk_info call is checked against it from then on.

FAQ

Questions about storage_get_disk_info

What does the storage_get_disk_info tool do? +

Get detailed disk/partition information including usage and mount points. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on storage_get_disk_info? +

Register the Aapanel MCP server in PolicyLayer and add a rule for storage_get_disk_info: 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 Aapanel. Nothing to install.

What risk level is storage_get_disk_info? +

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

Can I rate-limit storage_get_disk_info? +

Yes. Add a rate_limit block to the storage_get_disk_info 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 storage_get_disk_info completely? +

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

storage_get_disk_info is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aapanel, and thousands of servers like it.

This server

All 282 Aapanel tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →