VPS_recreateVirtualMachineV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Destructive

Parameters 52 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-recreatevirtualmachinev1.md

WHAT IT DOES

What VPS_recreateVirtualMachineV1 does on Hostinger Api

AI agents call VPS_recreateVirtualMachineV1 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
`password`	string	—	Root password for the virtual machine. If not provided, random password will be generated. Password will not be shown in the response.
`template_id`	integer	Yes	Template ID
`panel_password`	string	—	Panel password for the panel-based OS template. If not provided, random password will be generated. If OS does not support panel_password this field will be ign
`virtualMachineId`	integer	Yes	Virtual Machine ID
`post_install_script_id`	integer	—	Post-install script to execute after virtual machine was recreated

Parameters from the server's own tool schema.

RISK

Why VPS_recreateVirtualMachineV1 is rated Critical

This tool irreversibly deletes all data on a virtual machine by wiping and reinstalling the OS, destroying snapshots, and resetting to initial state. The description explicitly states the operation is irreversible and results in total data loss. This meets the Destructive category definition of actions that cannot be undone.

From the tool's definition Recreate a virtual machine from scratch. The recreation process involves reinstalling the operating system and resetting the virtual machine to its initial state. Snapshots, if there are any, will be deleted.

Risk signalsHandles credentials or secrets (password) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs VPS_recreateVirtualMachineV1 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_recreateVirtualMachineV1, this is the rule to start with:

VPS_recreateVirtualMachineV1 Hidden

VPS_recreateVirtualMachineV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "VPS_recreateVirtualMachineV1"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_recreateVirtualMachineV1 call is checked against it from then on.

FAQ

Questions about VPS_recreateVirtualMachineV1

What does the VPS_recreateVirtualMachineV1 tool do? +

Recreate a virtual machine from scratch. The recreation process involves reinstalling the operating system and resetting the virtual machine to its initial state. Snapshots, if there are any, will be deleted. Password Requirements Password will be checked against leaked password databases. Requirements for the password are: - At least 12 characters long - At least one uppercase letter - At least one lowercase letter - At least one number - Is not leaked publicly This operation is irreversible and will result in the loss of all data stored on the virtual machine! Use this endpoint to completely rebuild VPS instances with fresh OS installation. 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.

What parameters does VPS_recreateVirtualMachineV1 accept? +

VPS_recreateVirtualMachineV1 accepts 5 parameters: password, template_id, panel_password, virtualMachineId, post_install_script_id. Required: template_id, virtualMachineId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on VPS_recreateVirtualMachineV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_recreateVirtualMachineV1: 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.

What risk level is VPS_recreateVirtualMachineV1? +

VPS_recreateVirtualMachineV1 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_recreateVirtualMachineV1? +

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

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

VPS_recreateVirtualMachineV1 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.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →