storage_get_disk_io
Get disk I/O statistics for a time range.
This record as markdown: /tools/aapanel-mcp/storage-get-disk-io.md
What storage_get_disk_io does on Aapanel
AI agents call storage_get_disk_io 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.
Why storage_get_disk_io is rated Low
This tool queries and returns disk I/O statistics for monitoring/diagnostics purposes. It reads system metrics without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an attacker gains visibility into I/O patterns but cannot compromise systems or data.
From the tool's definition Tool name contains 'get' and description states 'Get disk I/O statistics' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs storage_get_disk_io 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_io, this is the rule to start with:
storage_get_disk_io 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 Aapanel, apply this rule, and every storage_get_disk_io call is checked against it from then on.
Questions about storage_get_disk_io
Get disk I/O statistics for a time range. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for storage_get_disk_io: 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.
storage_get_disk_io 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 storage_get_disk_io 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 storage_get_disk_io. 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.
storage_get_disk_io 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.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue