# vps_firewall_list

Get all firewalls.

Agent View of the PolicyLayer registry record for `vps_firewall_list`. HTML page: https://policylayer.com/tools/hostinger-mcp/vps-firewall-list

## Facts

- Tool: `vps_firewall_list`
- Server: Hostinger (`idugeni/hostinger-mcp`) — https://policylayer.com/tools/hostinger-mcp.md
- Homepage: https://github.com/idugeni/hostinger-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "vps_firewall_list",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hostinger:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "vps_firewall_list": {}
  }
}
```

## Other tools on Hostinger (283)

- `agency_cache_clear` — Destructive — https://policylayer.com/tools/hostinger-mcp/agency-cache-clear.md
- `agency_cron_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/agency-cron-delete.md
- `agency_db_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/agency-db-delete.md
- `agency_db_delete_user` — Destructive — https://policylayer.com/tools/hostinger-mcp/agency-db-delete-user.md
- `agency_website_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/agency-website-delete.md
- `billing_delete_payment_method` — Destructive — https://policylayer.com/tools/hostinger-mcp/billing-delete-payment-method.md
- `clear_api_cache` — Destructive — https://policylayer.com/tools/hostinger-mcp/clear-api-cache.md
- `dns_delete_records` — Destructive — https://policylayer.com/tools/hostinger-mcp/dns-delete-records.md
- `dns_reset_records` — Destructive — https://policylayer.com/tools/hostinger-mcp/dns-reset-records.md
- `domains_delete_forwarding` — Destructive — https://policylayer.com/tools/hostinger-mcp/domains-delete-forwarding.md
- `domains_delete_whois_profile` — Destructive — https://policylayer.com/tools/hostinger-mcp/domains-delete-whois-profile.md
- `ecommerce_stores_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/ecommerce-stores-delete.md
- `hosting_cron_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/hosting-cron-delete.md
- `hosting_db_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/hosting-db-delete.md
- `hosting_db_remote_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/hosting-db-remote-delete.md
- `hosting_parked_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/hosting-parked-delete.md
- `hosting_subdomains_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/hosting-subdomains-delete.md
- `hosting_websites_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/hosting-websites-delete.md
- `mail_aliases_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-aliases-delete.md
- `mail_autoreplies_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-autoreplies-delete.md
- `mail_catchalls_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-catchalls-delete.md
- `mail_forwarders_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-forwarders-delete.md
- `mail_mailboxes_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-mailboxes-delete.md
- `mail_tokens_revoke` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-tokens-revoke.md
- `mail_webhooks_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/mail-webhooks-delete.md
- `reach_contacts_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/reach-contacts-delete.md
- `vps_delete_snapshot` — Destructive — https://policylayer.com/tools/hostinger-mcp/vps-delete-snapshot.md
- `vps_docker_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/vps-docker-delete.md
- `vps_firewall_delete` — Destructive — https://policylayer.com/tools/hostinger-mcp/vps-firewall-delete.md
- `vps_firewall_delete_rule` — Destructive — https://policylayer.com/tools/hostinger-mcp/vps-firewall-delete-rule.md
- …and 253 more: https://policylayer.com/tools/hostinger-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=hostinger-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/hostinger-mcp