vps_firewall_get

Get firewall details with rules.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/vps-firewall-get.md

WHAT IT DOES

What vps_firewall_get does on Hostinger

AI agents call vps_firewall_get 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.

RISK

Why vps_firewall_get is rated Low

This tool retrieves firewall configuration and rules without side effects. No data is created, modified, deleted, or destroyed. It is a straightforward read operation with minimal risk if misused by an AI agent—worst case being information disclosure of existing firewall rules.

From the tool's definition Tool name 'vps_firewall_get' and description 'Get firewall details with rules' indicate retrieval/query operation with 'Get' verb and no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vps_firewall_get 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_get, this is the rule to start with:

vps_firewall_get Allowed

vps_firewall_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vps_firewall_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every vps_firewall_get call is checked against it from then on.

FAQ

Questions about vps_firewall_get

What does the vps_firewall_get tool do? +

Get firewall details with rules. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vps_firewall_get? +

Register the Hostinger MCP server in PolicyLayer and add a rule for vps_firewall_get: 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.

What risk level is vps_firewall_get? +

vps_firewall_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vps_firewall_get? +

Yes. Add a rate_limit block to the vps_firewall_get 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.

How do I block vps_firewall_get completely? +

Set action: deny in the PolicyLayer policy for vps_firewall_get. 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.

What MCP server provides vps_firewall_get? +

vps_firewall_get 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.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →