VPS_activateFirewallV1
Activate a firewall for a specified virtual machine. Only one firewall can be active for a virtual machine at a time. Use this endpoint to apply firewall rules to VPS instances.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-activatefirewallv1.md
What VPS_activateFirewallV1 does on Hostinger Api
AI agents invoke VPS_activateFirewallV1 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.
Why VPS_activateFirewallV1 is rated High
Activating a firewall changes the network security configuration of a VPS instance, triggering an external operation that affects traffic filtering rules. This is an Execute action with high severity because misconfiguration could block legitimate traffic or expose the server to threats.
From the tool's definition Activate a firewall for a specified virtual machine... apply firewall rules to VPS instances
Attacks that exploit this kind of access
The rule that runs VPS_activateFirewallV1 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_activateFirewallV1, this is the rule to start with:
VPS_activateFirewallV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_activateFirewallV1 call is checked against it from then on.
Questions about VPS_activateFirewallV1
Activate a firewall for a specified virtual machine. Only one firewall can be active for a virtual machine at a time. Use this endpoint to apply 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.
VPS_activateFirewallV1 accepts 2 parameters: firewallId, virtualMachineId. Required: firewallId, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_activateFirewallV1: 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.
VPS_activateFirewallV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the VPS_activateFirewallV1 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.
Set action: deny in the PolicyLayer policy for VPS_activateFirewallV1. 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.
VPS_activateFirewallV1 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.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue