site_stats_load_and_flow
Get system load average and upstream traffic flow.
This record as markdown: /tools/aapanel-mcp/site-stats-load-and-flow.md
What site_stats_load_and_flow does on Aapanel
AI agents call site_stats_load_and_flow 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 site_stats_load_and_flow is rated Low
This tool only queries and returns monitoring metrics (load average and traffic statistics). It has no capability to modify, execute, delete, or move resources. The read-only nature and purely informational purpose place it firmly in the Read category with low severity, as misuse would only expose performance data without enabling further attacks.
From the tool's definition The tool description states 'Get system load average and upstream traffic flow' — both are passive retrieval operations with no modification or execution of systems.
Attacks that exploit this kind of access
The rule that runs site_stats_load_and_flow 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 site_stats_load_and_flow, this is the rule to start with:
site_stats_load_and_flow 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 site_stats_load_and_flow call is checked against it from then on.
Questions about site_stats_load_and_flow
Get system load average and upstream traffic flow. 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 site_stats_load_and_flow: 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.
site_stats_load_and_flow 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 site_stats_load_and_flow 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 site_stats_load_and_flow. 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.
site_stats_load_and_flow 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