VPS_getDataCenterListV1

Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances.

SERVERHostinger Api SOURCEhostinger-api-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/io-github-hostinger-hostinger-api-mcp/vps-getdatacenterlistv1.md

WHAT IT DOES

What VPS_getDataCenterListV1 does on Hostinger Api

AI agents call VPS_getDataCenterListV1 to retrieve information from Hostinger Api 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_getDataCenterListV1 is rated Low

This tool retrieves static informational data about VPS data center locations. It performs a read-only operation with no ability to modify, execute code, delete data, or affect financial systems. The blast radius of misuse is minimal—an agent could only view available datacenter options, which is non-sensitive infrastructure metadata.

From the tool's definition Tool name contains 'get' and description states 'Retrieve all available data centers' — a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs VPS_getDataCenterListV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For VPS_getDataCenterListV1, this is the rule to start with:

VPS_getDataCenterListV1 Allowed

VPS_getDataCenterListV1 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_getDataCenterListV1": {}
  }
}

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

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

FAQ

Questions about VPS_getDataCenterListV1

What does the VPS_getDataCenterListV1 tool do? +

Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on VPS_getDataCenterListV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for VPS_getDataCenterListV1: 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 Api. Nothing to install.

What risk level is VPS_getDataCenterListV1? +

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

Can I rate-limit VPS_getDataCenterListV1? +

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

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

VPS_getDataCenterListV1 is provided by the Hostinger Api MCP server (hostinger-api-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 Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

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