site_stats_request_count_qps

Get real-time request count and QPS (queries per second) across all sites.

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/site-stats-request-count-qps.md

WHAT IT DOES

What site_stats_request_count_qps does on Aapanel

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

This tool retrieves real-time statistics about website traffic and performance metrics. It queries existing data without modifying, deleting, or executing any operations. The worst-case misuse would be information disclosure about site traffic patterns, which is low severity. No side effects or irreversible actions are possible.

From the tool's definition Tool name 'site_stats_request_count_qps' and description 'Get real-time request count and QPS (queries per second) across all sites' indicate data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

site_stats_request_count_qps Allowed

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

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

FAQ

Questions about site_stats_request_count_qps

What does the site_stats_request_count_qps tool do? +

Get real-time request count and QPS (queries per second) across all sites. 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 site_stats_request_count_qps? +

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

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

Can I rate-limit site_stats_request_count_qps? +

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

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

site_stats_request_count_qps 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

The MCP Attack Database →

Guides

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