VPS_createNewFirewallV1
Create a new firewall. Use this endpoint to set up new firewall configurations for VPS security.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-createnewfirewallv1.md
What VPS_createNewFirewallV1 does on Hostinger Api
AI agents use VPS_createNewFirewallV1 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 |
|---|---|---|---|
name | string | Yes | name parameter |
Parameters from the server's own tool schema.
Why VPS_createNewFirewallV1 is rated Medium
The tool creates/modifies firewall configurations, which is a Write operation. Severity is high because misconfigured firewalls can lock out legitimate traffic, disrupt services, or create unintended security gaps on a VPS, but the action is reversible (the firewall can be deleted or reconfigured). Not Destructive because firewall creation doesn't irreversibly delete data.
From the tool's definition Tool name contains 'create' and description states 'Create a new firewall' and 'set up new firewall configurations'. These are reversible configuration changes that modify VPS security settings.
Attacks that exploit this kind of access
The rule that runs VPS_createNewFirewallV1 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_createNewFirewallV1, this is the rule to start with:
VPS_createNewFirewallV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_createNewFirewallV1 call is checked against it from then on.
Questions about VPS_createNewFirewallV1
Create a new firewall. Use this endpoint to set up new firewall configurations for VPS security. 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.
VPS_createNewFirewallV1 accepts 1 parameter: name. Required: name. 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_createNewFirewallV1: 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_createNewFirewallV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the VPS_createNewFirewallV1 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_createNewFirewallV1. 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_createNewFirewallV1 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.
This server
Across the catalogue