vps_list

Get list of all virtual machines.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What vps_list does on Hostinger

AI agents call vps_list to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why vps_list is rated Low

This tool queries and returns information about existing virtual machines without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk if misused—an agent could at worst retrieve information about the infrastructure it should already have authorized access to.

From the tool's definition Tool name 'vps_list' and description 'Get list of all virtual machines' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vps_list Allowed

vps_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vps_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vps_list

What does the vps_list tool do? +

Get list of all virtual machines. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vps_list? +

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

vps_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vps_list? +

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

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

vps_list 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 →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →