vps_recreate
Recreate (reinstall) a virtual machine. DESTROYS ALL DATA.
This record as markdown: /tools/hostinger-mcp/vps-recreate.md
What vps_recreate does on Hostinger
AI agents call vps_recreate 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_recreate is rated Critical
The tool explicitly states it destroys all data on the virtual machine during reinstallation. This is an irreversible operation with maximum blast radius — an entire VPS and all its contents are wiped. Highest severity (critical) is warranted.
From the tool's definition "Recreate (reinstall) a virtual machine. DESTROYS ALL DATA."
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs vps_recreate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vps_recreate, this is the rule to start with:
vps_recreate 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, apply this rule, and every vps_recreate call is checked against it from then on.
Questions about vps_recreate
Recreate (reinstall) a virtual machine. DESTROYS ALL DATA. 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.
Register the Hostinger MCP server in PolicyLayer and add a rule for vps_recreate: 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.
vps_recreate 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_recreate 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_recreate. 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_recreate 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.
Across the catalogue