VPS_updateFirewallRuleV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 66 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-updatefirewallrulev1.md

WHAT IT DOES

What VPS_updateFirewallRuleV1 does on Hostinger Api

AI agents use VPS_updateFirewallRuleV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`port`	string	Yes	Port or port range, ex: 1024:2048
`ruleId`	integer	Yes	Firewall Rule ID
`source`	string	Yes	source parameter
`protocol`	string	Yes	protocol parameter
`firewallId`	integer	Yes	Firewall ID
`source_detail`	string	Yes	IP range, CIDR, single IP or `any`

Parameters from the server's own tool schema.

RISK

Why VPS_updateFirewallRuleV1 is rated Medium

This tool modifies an existing firewall rule (Write), but the blast radius is high because changing firewall rules can expose or block access to all VMs using that firewall, and it causes sync loss requiring manual intervention. It does not irreversibly delete data, so Destructive does not apply, but the security implications make severity high.

From the tool's definition Update a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs VPS_updateFirewallRuleV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For VPS_updateFirewallRuleV1, this is the rule to start with:

VPS_updateFirewallRuleV1 Rate-limited

VPS_updateFirewallRuleV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "VPS_updateFirewallRuleV1": {
      "limits": [
        {
          "counter": "vps_updatefirewallrulev1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about VPS_updateFirewallRuleV1

What does the VPS_updateFirewallRuleV1 tool do? +

Update a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to modify existing firewall rules. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does VPS_updateFirewallRuleV1 accept? +

VPS_updateFirewallRuleV1 accepts 6 parameters: port, ruleId, source, protocol, firewallId, source_detail. Required: port, ruleId, source, protocol, firewallId, source_detail. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_updateFirewallRuleV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_updateFirewallRuleV1: 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 Api. Nothing to install.

What risk level is VPS_updateFirewallRuleV1? +

VPS_updateFirewallRuleV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit VPS_updateFirewallRuleV1? +

Yes. Add a rate_limit block to the VPS_updateFirewallRuleV1 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_updateFirewallRuleV1 completely? +

Set action: deny in the PolicyLayer policy for VPS_updateFirewallRuleV1. 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_updateFirewallRuleV1? +

VPS_updateFirewallRuleV1 is provided by the Hostinger Api MCP server (hostinger-api-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 Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →