This record as markdown: /tools/hostinger-mcp/vps-firewall-list.md
What vps_firewall_list does on Hostinger
AI agents call vps_firewall_list to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vps_firewall_list is rated Low
This tool retrieves or queries firewall data (list operation) with no side effects. It falls squarely into the Read category. Severity is low because listing firewall rules is informational and carries minimal blast radius even if an agent retrieves this data inappropriately—no systems are harmed or modified by reading firewall information.
From the tool's definition Tool name 'vps_firewall_list' and description 'Get all firewalls' indicate a read-only query operation that retrieves firewall configuration data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs vps_firewall_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vps_firewall_list, this is the rule to start with:
vps_firewall_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 Hostinger, apply this rule, and every vps_firewall_list call is checked against it from then on.
Questions about vps_firewall_list
Get all firewalls. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for vps_firewall_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 Hostinger. Nothing to install.
vps_firewall_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 vps_firewall_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 vps_firewall_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.
vps_firewall_list is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue