firewall_get_list
List firewall rules (ports and IP rules).
This record as markdown: /tools/aapanel-mcp/firewall-get-list.md
What firewall_get_list does on Aapanel
AI agents call firewall_get_list 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 firewall_get_list is rated Low
This tool retrieves and displays firewall configuration (ports and IP rules) without altering state, triggering actions, or risking data loss. It is a straightforward read operation with minimal risk even if misused by an AI agent, as viewing firewall rules poses no security threat comparable to modifying or deleting them.
From the tool's definition Tool name contains 'get_list' and description states 'List firewall rules' — a query operation that retrieves existing data without modification or execution.
Attacks that exploit this kind of access
The rule that runs firewall_get_list 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 firewall_get_list, this is the rule to start with:
firewall_get_list 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 firewall_get_list call is checked against it from then on.
Questions about firewall_get_list
List firewall rules (ports and IP rules). 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 firewall_get_list: 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.
firewall_get_list 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 firewall_get_list 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 firewall_get_list. 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.
firewall_get_list 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