VPS_syncFirewallV1

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 22 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-syncfirewallv1.md

WHAT IT DOES

What VPS_syncFirewallV1 does on Hostinger Api

AI agents invoke VPS_syncFirewallV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`firewallId`	integer	Yes	Firewall ID
`virtualMachineId`	integer	Yes	Virtual Machine ID

Parameters from the server's own tool schema.

RISK

Why VPS_syncFirewallV1 is rated High

This tool triggers an external operation that pushes firewall rule changes to a live VPS instance. It executes a network security policy enforcement action — if misused by an AI agent, it could apply incorrect firewall rules, potentially exposing or locking down the server, making it a high-severity Execute action.

From the tool's definition Sync a firewall for a specified virtual machine... apply updated firewall rules to VPS instances

Attacks that exploit this kind of access

RECOMMENDED RULE

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

VPS_syncFirewallV1 Rate-limited

VPS_syncFirewallV1 stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_syncFirewallV1": {
      "limits": [
        {
          "counter": "vps_syncfirewallv1_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_syncFirewallV1 call is checked against it from then on.

FAQ

Questions about VPS_syncFirewallV1

What does the VPS_syncFirewallV1 tool do? +

Sync a firewall for a specified virtual machine. Firewall can lose sync with virtual machine if the firewall has new rules added, removed or updated. Use this endpoint to apply updated firewall rules to VPS instances. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does VPS_syncFirewallV1 accept? +

VPS_syncFirewallV1 accepts 2 parameters: firewallId, virtualMachineId. Required: firewallId, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_syncFirewallV1? +

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

VPS_syncFirewallV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit VPS_syncFirewallV1? +

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

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

VPS_syncFirewallV1 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →