site_get_traffic_limit
Get traffic/rate limiting configuration for a site.
This record as markdown: /tools/aapanel-mcp/site-get-traffic-limit.md
What site_get_traffic_limit does on Aapanel
AI agents call site_get_traffic_limit 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_get_traffic_limit is rated Low
This is a read-only operation that queries existing configuration data without side effects. It retrieves information about traffic limits for a site, making it a simple information retrieval tool with minimal risk.
From the tool's definition Tool name 'site_get_traffic_limit' with verb 'get' and description states it retrieves traffic/rate limiting configuration. No modification, deletion, or execution indicated.
Attacks that exploit this kind of access
The rule that runs site_get_traffic_limit 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_get_traffic_limit, this is the rule to start with:
site_get_traffic_limit 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_get_traffic_limit call is checked against it from then on.
Questions about site_get_traffic_limit
Get traffic/rate limiting configuration for a site. 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_get_traffic_limit: 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_get_traffic_limit 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_get_traffic_limit 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_get_traffic_limit. 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_get_traffic_limit 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