VPS_restoreBackupV1
Restore a backup for a specified virtual machine. The system will then initiate the restore process, which may take some time depending on the size of the backup. All data on the virtual machine will be overwritten with the data from the backup. Use this endpoint to recover VPS data from backup p...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-restorebackupv1.md
What VPS_restoreBackupV1 does on Hostinger Api
AI agents call VPS_restoreBackupV1 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 |
|---|---|---|---|
backupId | integer | Yes | Backup ID |
virtualMachineId | integer | Yes | Virtual Machine ID |
Parameters from the server's own tool schema.
Why VPS_restoreBackupV1 is rated Critical
Restoring a backup irreversibly overwrites all current data on the virtual machine. Any changes made after the backup point will be permanently lost. This is a destructive, non-reversible operation with a critical blast radius as it affects an entire VPS instance.
From the tool's definition All data on the virtual machine will be overwritten with the data from the backup.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs VPS_restoreBackupV1 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_restoreBackupV1, this is the rule to start with:
VPS_restoreBackupV1 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_restoreBackupV1 call is checked against it from then on.
Questions about VPS_restoreBackupV1
Restore a backup for a specified virtual machine. The system will then initiate the restore process, which may take some time depending on the size of the backup. All data on the virtual machine will be overwritten with the data from the backup. Use this endpoint to recover VPS data from backup points. 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_restoreBackupV1 accepts 2 parameters: backupId, virtualMachineId. Required: backupId, virtualMachineId. 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_restoreBackupV1: 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_restoreBackupV1 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_restoreBackupV1 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_restoreBackupV1. 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_restoreBackupV1 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