This record as markdown: /tools/aapanel-mcp/waf-get-logs.md
What waf_get_logs does on Aapanel
AI agents call waf_get_logs 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_logs is rated Low
This tool retrieves historical log data from the WAF (Web Application Firewall) system. Retrieving logs is a passive, non-destructive operation that does not modify, execute, or delete any data. It poses minimal risk as an AI agent using this tool would only gain visibility into past security events, not perform actions that could affect system state or security posture.
From the tool's definition Tool name is 'waf_get_logs' and description states 'Get WAF attack/interception logs.' The verb 'Get' and the query nature of retrieving logs indicate a read-only operation with no data modification, creation, or side effects.
Attacks that exploit this kind of access
The rule that runs waf_get_logs 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_logs, this is the rule to start with:
waf_get_logs 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_logs call is checked against it from then on.
Questions about waf_get_logs
Get WAF attack/interception logs. 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_logs: 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_logs 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_logs 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_logs. 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_logs 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