VPS_replaceAllFirewallRulesInGroupV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 32 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-replaceallfirewallrulesingroupv1.md

WHAT IT DOES

What VPS_replaceAllFirewallRulesInGroupV1 does on Hostinger Api

AI agents use VPS_replaceAllFirewallRulesInGroupV1 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
`sync`	boolean	—	Synchronize the firewall group to all its virtual machines after replacing the rules
`rules`	array	Yes	The complete set of firewall rules that atomically replaces all existing rules in the group
`firewallId`	integer	Yes	Firewall ID

Parameters from the server's own tool schema.

RISK

Why VPS_replaceAllFirewallRulesInGroupV1 is rated Medium

An AI agent can call VPS_replaceAllFirewallRulesInGroupV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_replaceAllFirewallRulesInGroupV1 Rate-limited

VPS_replaceAllFirewallRulesInGroupV1 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_replaceAllFirewallRulesInGroupV1": {
      "limits": [
        {
          "counter": "vps_replaceallfirewallrulesingroupv1_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_replaceAllFirewallRulesInGroupV1 call is checked against it from then on.

FAQ

Questions about VPS_replaceAllFirewallRulesInGroupV1

What does the VPS_replaceAllFirewallRulesInGroupV1 tool do? +

Replaces all firewall rules within a specified firewall group with the provided set of rules in a single atomic operation, instead of creating or deleting rules one by one. Any virtual machine using this firewall group will need to be synchronized after replacing rules; pass the "sync" parameter to trigger synchronization immediately. 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_replaceAllFirewallRulesInGroupV1 accept? +

VPS_replaceAllFirewallRulesInGroupV1 accepts 3 parameters: sync, rules, firewallId. Required: rules, firewallId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_replaceAllFirewallRulesInGroupV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_replaceAllFirewallRulesInGroupV1: 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_replaceAllFirewallRulesInGroupV1? +

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

Can I rate-limit VPS_replaceAllFirewallRulesInGroupV1? +

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

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

VPS_replaceAllFirewallRulesInGroupV1 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 382 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

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