cpu_get_io_stats

Get CPU I/O statistics for a time range.

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/cpu-get-io-stats.md

WHAT IT DOES

What cpu_get_io_stats does on Aapanel

AI agents call cpu_get_io_stats 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 cpu_get_io_stats is rated Low

This tool queries and returns CPU I/O statistics without modifying any system state or triggering external operations. It has no blast radius if misused by an AI agent—the worst outcome is access to performance monitoring data that may already be available to authenticated users. Classification as Read is appropriate.

From the tool's definition The tool name 'cpu_get_io_stats' and description 'Get CPU I/O statistics for a time range' indicate a retrieval operation with no side effects. The verb 'Get' and the passive data retrieval context confirm this is a read-only operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cpu_get_io_stats 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 cpu_get_io_stats, this is the rule to start with:

cpu_get_io_stats Allowed

cpu_get_io_stats 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": {
    "cpu_get_io_stats": {}
  }
}

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 cpu_get_io_stats call is checked against it from then on.

FAQ

Questions about cpu_get_io_stats

What does the cpu_get_io_stats tool do? +

Get CPU 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.

How do I enforce a policy on cpu_get_io_stats? +

Register the Aapanel MCP server in PolicyLayer and add a rule for cpu_get_io_stats: 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 cpu_get_io_stats? +

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

Can I rate-limit cpu_get_io_stats? +

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

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

cpu_get_io_stats 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 →