batch_vps_restart

Restart multiple VPS instances at once.

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/batch-vps-restart.md

WHAT IT DOES

What batch_vps_restart does on Hostinger

AI agents invoke batch_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 batch_vps_restart is rated High

Restarting VPS instances is an external operation with system-level effects that depend on which instances are targeted (the arguments). While restarts are typically reversible and not destructive, they trigger significant infrastructure changes—potential downtime, service interruption, and cascading effects on hosted applications.

From the tool's definition Tool name explicitly states 'restart' on 'multiple VPS instances'. Description confirms it performs batch restart operations on multiple servers simultaneously.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

batch_vps_restart Rate-limited

batch_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": {
    "batch_vps_restart": {
      "limits": [
        {
          "counter": "batch_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 batch_vps_restart call is checked against it from then on.

FAQ

Questions about batch_vps_restart

What does the batch_vps_restart tool do? +

Restart multiple VPS instances at once. 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 batch_vps_restart? +

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

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

Can I rate-limit batch_vps_restart? +

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

Set action: deny in the PolicyLayer policy for batch_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 batch_vps_restart? +

batch_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

qt_batch on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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