hosting_listAvailableDatacentersV1
Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-listavailabledatacentersv1.md
What hosting_listAvailableDatacentersV1 does on Hostinger Api
AI agents call hosting_listAvailableDatacentersV1 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
order_id | integer | Yes | Order ID |
Parameters from the server's own tool schema.
Why hosting_listAvailableDatacentersV1 is rated Low
This tool retrieves datacenter information without side effects. It performs a read-only query operation that returns available options, matching the 'Read' category definition (retrieves or queries data; no side effects). The blast radius is minimal as misuse would only return datacenter data without enabling any harmful actions.
From the tool's definition Tool name contains 'list' and description states 'Retrieve a list of datacenters' with no mention of modification, deletion, or execution of external operations. The operation is purely informational.
Attacks that exploit this kind of access
The rule that runs hosting_listAvailableDatacentersV1 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 hosting_listAvailableDatacentersV1, this is the rule to start with:
hosting_listAvailableDatacentersV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_listAvailableDatacentersV1 call is checked against it from then on.
Questions about hosting_listAvailableDatacentersV1
Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_listAvailableDatacentersV1 accepts 1 parameter: order_id. Required: order_id. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_listAvailableDatacentersV1: 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.
hosting_listAvailableDatacentersV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hosting_listAvailableDatacentersV1 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.
Set action: deny in the PolicyLayer policy for hosting_listAvailableDatacentersV1. 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.
hosting_listAvailableDatacentersV1 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.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue