# VPS_startRecoveryModeV1

Initiate recovery mode for a specified virtual machine. Recovery mode is a special state that allows users to perform system rescue operations, such as repairing file systems, recovering data, or troubleshooting issues that prevent the virtual machine from booting normally. Virtual machine will boot recovery disk image and original disk image will be mounted in /mnt directory. Use this endpoint to enable system rescue operations on VPS instances.

Agent View of the PolicyLayer registry record for `VPS_startRecoveryModeV1`. HTML page: https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-startrecoverymodev1

## Facts

- Tool: `VPS_startRecoveryModeV1`
- Server: Hostinger Api (`hostinger-api-mcp`) — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp.md
- Install: `npx -y hostinger-api-mcp`
- Homepage: https://github.com/hostinger/api-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `root_password` | string | yes | Temporary root password for recovery mode |
| `virtualMachineId` | integer | yes | Virtual Machine ID |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "VPS_startRecoveryModeV1",
    "arguments": {
      "root_password": "<root_password>",
      "virtualMachineId": 0
    }
  }
}
```

## Why VPS_startRecoveryModeV1 is rated High

This tool triggers a state change on a VPS instance (booting into recovery mode, mounting disks), which is an execute-class operation. While not immediately destructive, recovery mode can be misused to access or modify systems inappropriately.

From the tool's own definition: "'Initiate recovery mode for a specified virtual machine' with effects of booting a recovery disk and mounting filesystems—these are external system operations with non-trivial side effects that depend on the target VM argument."

## Use case

AI agents invoke VPS_startRecoveryModeV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hostinger Api:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "VPS_startRecoveryModeV1": {
      "limits": [
        {
          "counter": "vps_startrecoverymodev1_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Hostinger Api (257)

- `agency-hosting_clearAgencyPlanWebsiteCacheV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-clearagencyplanwebsitecachev1.md
- `agency-hosting_deleteAgencyPlanWebsiteCronJobV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitecronjobv1.md
- `agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitedatabaseuserv1.md
- `agency-hosting_deleteAgencyPlanWebsiteDatabaseV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitedatabasev1.md
- `agency-hosting_deleteAgencyPlanWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitev1.md
- `agencyHosting_deployNodeStaticWebsite` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agencyhosting-deploynodestaticwebsite.md
- `agencyHosting_deployPhpApplication` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agencyhosting-deployphpapplication.md
- `billing_deletePaymentMethodV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/billing-deletepaymentmethodv1.md
- `DNS_deleteDNSRecordsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/dns-deletednsrecordsv1.md
- `DNS_resetDNSRecordsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/dns-resetdnsrecordsv1.md
- `domains_deleteDomainForwardingV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-deletedomainforwardingv1.md
- `domains_deleteWHOISProfileV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-deletewhoisprofilev1.md
- `ecommerce_deleteStoreV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/ecommerce-deletestorev1.md
- `hosting_clearWebsiteCacheV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-clearwebsitecachev1.md
- `hosting_deleteAccountCronJobV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountcronjobv1.md
- `hosting_deleteAccountDatabaseRemoteConnectionV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountdatabaseremoteconnectionv1.md
- `hosting_deleteAccountDatabaseV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountdatabasev1.md
- `hosting_deleteWebsiteParkedDomainV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsiteparkeddomainv1.md
- `hosting_deleteWebsiteSubdomainV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsitesubdomainv1.md
- `hosting_deleteWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsitev1.md
- `hosting_deleteWordPressInstallationV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewordpressinstallationv1.md
- `hosting_uninstallWordPressPluginsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-uninstallwordpresspluginsv1.md
- `hosting_uninstallWordPressThemesV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-uninstallwordpressthemesv1.md
- `mail_deleteMailboxV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/mail-deletemailboxv1.md
- `mail_deleteWebhookV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/mail-deletewebhookv1.md
- `mail_revokeAPITokenV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/mail-revokeapitokenv1.md
- `reach_deleteAContactV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/reach-deleteacontactv1.md
- `VPS_deleteFirewallRuleV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deletefirewallrulev1.md
- `VPS_deleteFirewallV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deletefirewallv1.md
- `VPS_deletePostInstallScriptV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deletepostinstallscriptv1.md
- …and 227 more: https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-hostinger-hostinger-api-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-hostinger-hostinger-api-mcp
