This record as markdown: /tools/aapanel-mcp/waf-get-sites.md
What waf_get_sites does on Aapanel
AI agents call waf_get_sites 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 waf_get_sites is rated Low
This tool retrieves/queries configuration data about which sites are protected by a Web Application Firewall. It is a read-only operation that returns information without modifying any state or triggering external actions. The blast radius of misuse is minimal—an attacker gains only informational data about WAF protection status, which does not enable direct compromise of systems.
From the tool's definition Tool name 'waf_get_sites' and description 'Get list of sites protected by WAF' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs waf_get_sites 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 waf_get_sites, this is the rule to start with:
waf_get_sites 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 waf_get_sites call is checked against it from then on.
Questions about waf_get_sites
Get list of sites protected by WAF. 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 waf_get_sites: 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.
waf_get_sites 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 waf_get_sites 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 waf_get_sites. 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.
waf_get_sites 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