vps_restart

Restart a virtual machine.

SERVERHostinger SOURCEidugeni/hostinger-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/vps-restart.md

WHAT IT DOES

What vps_restart does on Hostinger

AI agents invoke vps_restart 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.

RISK

Why vps_restart is rated High

Restarting a VPS is an execute action—it runs an operation on external infrastructure. While not destructive (data is preserved), it has significant blast radius: service downtime, disrupted operations, and potential cascading failures. An AI agent with misuse could restart critical production VMs. Severity is high due to availability impact.

From the tool's definition Tool name: 'vps_restart'. Description: 'Restart a virtual machine.' The action directly triggers an external operation (VM restart) whose effects depend on which VPS is targeted via arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vps_restart Rate-limited

vps_restart stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vps_restart

What does the vps_restart tool do? +

Restart a virtual machine. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vps_restart? +

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

vps_restart is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vps_restart? +

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

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

vps_restart 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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →