agency-hosting_listAvailableDatacentersV1
Lists the datacenters available for provisioning a new website on the given Agency Plan hosting order. Each datacenter includes a pinger_url you can ping from the client to measure round-trip latency; comparing the results across datacenters lets you pick the nearest one (lowest ping) before choo...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-listavailabledatacentersv1.md
What agency-hosting_listAvailableDatacentersV1 does on Hostinger Api
AI agents call agency-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 | Agency Plan order ID |
Parameters from the server's own tool schema.
Why agency-hosting_listAvailableDatacentersV1 is rated Low
Tool retrieves datacenter information without modifying or executing operations.
From the tool's definition Lists the datacenters available; includes pinger_url for measurement.
Attacks that exploit this kind of access
The rule that runs agency-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 agency-hosting_listAvailableDatacentersV1, this is the rule to start with:
agency-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 agency-hosting_listAvailableDatacentersV1 call is checked against it from then on.
Questions about agency-hosting_listAvailableDatacentersV1
Lists the datacenters available for provisioning a new website on the given Agency Plan hosting order. Each datacenter includes a pinger_url you can ping from the client to measure round-trip latency; comparing the results across datacenters lets you pick the nearest one (lowest ping) before choosing its code as the datacenter_code when creating a website setup. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
agency-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 agency-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.
agency-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 agency-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 agency-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.
agency-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