vps_restore_backup

Restore a backup.

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-restore-backup.md

WHAT IT DOES

What vps_restore_backup does on Hostinger

AI agents call vps_restore_backup 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.

RISK

Why vps_restore_backup is rated Critical

Restoring a backup is a destructive operation because it replaces the current live system state with an older snapshot, permanently discarding any changes, files, databases, or configurations made after the backup point. This cannot be undone and has a critical blast radius as it affects the entire VPS environment.

From the tool's definition 'Restore a backup' — restoring a backup overwrites the current state of the VPS irreversibly, destroying all data written since the backup was taken.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vps_restore_backup Hidden

vps_restore_backup 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_restore_backup"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vps_restore_backup

What does the vps_restore_backup tool do? +

Restore a backup. 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_restore_backup? +

Register the Hostinger MCP server in PolicyLayer and add a rule for vps_restore_backup: 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_restore_backup? +

vps_restore_backup 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_restore_backup? +

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

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

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

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools → Critical-risk tools on this server →

Across the catalogue

create_full_backup on Android Forensics ADB MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →