vps_recovery_start

What vps_recovery_start does on Hostinger

AI agents invoke vps_recovery_start to trigger actions in Hostinger. 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.

Why vps_recovery_start is rated High

This is an Execute category tool because it triggers an external operation (VPS system state transition) whose consequences depend on what an agent does next in recovery mode. While not immediately destructive, booting into recovery mode grants elevated access to the entire VPS and enables potentially dangerous follow-up actions (data modification, deletion, credential exposure).

From the tool's definition Tool performs 'Boot VPS into recovery mode' - a system-level operation that changes the operational state of infrastructure. Recovery mode enables administrative access and system reconfiguration with effects that depend on subsequent user actions.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vps_recovery_start": {
      "limits": [
        {
          "counter": "vps_recovery_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about vps_recovery_start