VPS_deleteFirewallV1
Delete a specified firewall. Any virtual machine that has this firewall activated will automatically have it deactivated. Use this endpoint to remove unused firewall configurations.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-deletefirewallv1.md
What VPS_deleteFirewallV1 does on Hostinger Api
AI agents call VPS_deleteFirewallV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
firewallId | integer | Yes | Firewall ID |
Parameters from the server's own tool schema.
Why VPS_deleteFirewallV1 is rated Critical
This tool permanently deletes firewall configurations, which is an irreversible destructive action. While not directly causing data loss, removing a firewall degrades security posture of dependent VMs. Destructive category applies because deletion cannot be reversed without manual reconfiguration.
From the tool's definition Tool name includes 'delete' and description states 'Delete a specified firewall' — this irreversibly removes firewall configurations. The side effect of automatic deactivation on associated VMs indicates permanent state changes that cannot be undone.
Attacks that exploit this kind of access
The rule that runs VPS_deleteFirewallV1 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_deleteFirewallV1, this is the rule to start with:
VPS_deleteFirewallV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_deleteFirewallV1 call is checked against it from then on.
Questions about VPS_deleteFirewallV1
Delete a specified firewall. Any virtual machine that has this firewall activated will automatically have it deactivated. Use this endpoint to remove unused firewall configurations. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
VPS_deleteFirewallV1 accepts 1 parameter: firewallId. Required: firewallId. 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_deleteFirewallV1: 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_deleteFirewallV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the VPS_deleteFirewallV1 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_deleteFirewallV1. 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_deleteFirewallV1 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