agency-hosting_getWebsiteSetupStatusV1
Returns the current status of an Agency Plan website setup started via the setups endpoint. Poll this endpoint using the setup_uuid returned from the provisioning request until status becomes completed, at which point website_uid identifies the new website.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-getwebsitesetupstatusv1.md
What agency-hosting_getWebsiteSetupStatusV1 does on Hostinger Api
AI agents call agency-hosting_getWebsiteSetupStatusV1 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 |
setup_uuid | string | Yes | Website setup UUID |
Parameters from the server's own tool schema.
Why agency-hosting_getWebsiteSetupStatusV1 is rated Low
Polls setup status and retrieves website information without modifying or executing operations.
From the tool's definition Returns the current status of an Agency Plan website setup
Attacks that exploit this kind of access
The rule that runs agency-hosting_getWebsiteSetupStatusV1 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_getWebsiteSetupStatusV1, this is the rule to start with:
agency-hosting_getWebsiteSetupStatusV1 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_getWebsiteSetupStatusV1 call is checked against it from then on.
Questions about agency-hosting_getWebsiteSetupStatusV1
Returns the current status of an Agency Plan website setup started via the setups endpoint. Poll this endpoint using the setup_uuid returned from the provisioning request until status becomes completed, at which point website_uid identifies the new website. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
agency-hosting_getWebsiteSetupStatusV1 accepts 2 parameters: order_id, setup_uuid. Required: order_id, setup_uuid. 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_getWebsiteSetupStatusV1: 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_getWebsiteSetupStatusV1 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_getWebsiteSetupStatusV1 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_getWebsiteSetupStatusV1. 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_getWebsiteSetupStatusV1 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