New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

vps_firewall_delete

Delete a firewall.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/vps-firewall-delete.md

What vps_firewall_delete does on Hostinger

AI agents call vps_firewall_delete to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why vps_firewall_delete is rated Critical

Deleting a firewall is an irreversible operation that removes network security controls. This has high blast radius if triggered accidentally or maliciously by an AI agent, potentially leaving VPS infrastructure unprotected. While not financial in nature, it qualifies as Destructive rather than Execute because the action itself (delete) cannot be undone and results in permanent loss of configuration.

From the tool's definition Tool name contains 'delete' and description states 'Delete a firewall.' This is an irreversible destructive action that removes firewall configuration entirely.

Questions about vps_firewall_delete

What does the vps_firewall_delete tool do? +

Delete a firewall. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on vps_firewall_delete? +

Register the Hostinger MCP server in PolicyLayer and add a rule for vps_firewall_delete: 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. Nothing to install.

What risk level is vps_firewall_delete? +

vps_firewall_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit vps_firewall_delete? +

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

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

vps_firewall_delete is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hostinger, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.