agency-hosting_provisionANewAgencyPlanWebsiteV1
Provisions a new website on one of your Agency Plan hosting orders. Choose the datacenter, stack (flavor), and PHP version for the site. Optionally attach your own domain — omit it, set it to null, or leave it unavailable and a free *.hostingersite.com subdomain is generated instead — and/or inst...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-provisionanewagencyplanwebsitev1.md
What agency-hosting_provisionANewAgencyPlanWebsiteV1 does on Hostinger Api
AI agents use agency-hosting_provisionANewAgencyPlanWebsiteV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Website type |
clone | object | — | Clone the new website from an existing website |
domain | string | — | Primary domain to attach to the website. Omit or set to null to get a free auto-generated *.hostingersite.com subdomain instead. |
flavor | string | Yes | Setup flavor: a specific WordPress version in the format `wp-<major>.<minor>` or `wp-<major>.<minor>.<patch>` (e.g. `wp-6.8.2`), or `php-fpm` for a plain PHP st |
order_id | integer | Yes | Agency Plan order ID |
settings | object | Yes | Website settings |
wordpress | object | — | WordPress installation options |
derive_domain | object | — | Derive the domain from an existing vhost |
datacenter_code | string | Yes | Datacenter code where the website should be provisioned. Available codes depend on live capacity and are not a fixed set. |
Parameters from the server's own tool schema.
Why agency-hosting_provisionANewAgencyPlanWebsiteV1 is rated Medium
An AI agent can call agency-hosting_provisionANewAgencyPlanWebsiteV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (wordpress.admin.password) · High parameter count (21 properties) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs agency-hosting_provisionANewAgencyPlanWebsiteV1 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_provisionANewAgencyPlanWebsiteV1, this is the rule to start with:
agency-hosting_provisionANewAgencyPlanWebsiteV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_provisionANewAgencyPlanWebsiteV1 call is checked against it from then on.
Questions about agency-hosting_provisionANewAgencyPlanWebsiteV1
Provisions a new website on one of your Agency Plan hosting orders. Choose the datacenter, stack (flavor), and PHP version for the site. Optionally attach your own domain — omit it, set it to null, or leave it unavailable and a free *.hostingersite.com subdomain is generated instead — and/or install WordPress by supplying the wordpress details (admin account, site title, and language). Common setups: - Plain PHP site: flavor set to php-fpm, with settings.php.version; omit wordpress and type. - WordPress site: flavor set to the desired WordPress version (e.g. wp-7.0), plus the wordpress block (admin account, title, language). - Static/Node.js frontend app: flavor set to php-fpm and type set to node-static. Provisioning runs in the background, so the response returns immediately with a setup UUID that identifies the job. The new website becomes reachable once provisioning finishes. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
agency-hosting_provisionANewAgencyPlanWebsiteV1 accepts 9 parameters: type, clone, domain, flavor, order_id, settings, wordpress, derive_domain, datacenter_code. Required: flavor, order_id, settings, datacenter_code. 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_provisionANewAgencyPlanWebsiteV1: 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_provisionANewAgencyPlanWebsiteV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agency-hosting_provisionANewAgencyPlanWebsiteV1 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_provisionANewAgencyPlanWebsiteV1. 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_provisionANewAgencyPlanWebsiteV1 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