hosting_installWordPressV1

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 104 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-installwordpressv1.md

WHAT IT DOES

What hosting_installWordPressV1 does on Hostinger Api

AI agents invoke hosting_installWordPressV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`domain`	string	Yes	Domain of the existing website where WordPress will be installed
`version`	string	—	WordPress core version to install. If omitted, the latest core version compatible with the account vhost PHP version is selected.
`database`	object	—	Optional. If the named database already exists, it will be used for this WordPress install. Otherwise a new database is created with a generated name and random
`language`	string	—	WordPress locale. Defaults to en_US when omitted.
`username`	string	Yes	username parameter
`directory`	string	—	Relative directory to install WordPress into. Defaults to the website root when omitted.
`overwrite`	boolean	—	When false (default), does not replace an existing installation. If WordPress is already installed on the domain/path, the async install job fails unless true.
`site_title`	string	Yes	Title of the WordPress site
`credentials`	object	Yes	WordPress admin credentials
`auto_updates`	string	—	WordPress core auto-update policy

Parameters from the server's own tool schema.

RISK

Why hosting_installWordPressV1 is rated High

This tool triggers an external installation operation on a hosting environment. It executes a WordPress installation process on a remote server, which is an external operation with significant side effects (modifying the server environment, potentially overwriting existing data if overwrite=true).

From the tool's definition Install WordPress on an existing website... This operation is asynchronous: a successful response only means the install job has been queued

Risk signalsAccepts file system path (directory) · Handles credentials or secrets (credentials) · High parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_installWordPressV1 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_installWordPressV1, this is the rule to start with:

hosting_installWordPressV1 Rate-limited

hosting_installWordPressV1 stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_installWordPressV1": {
      "limits": [
        {
          "counter": "hosting_installwordpressv1_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about hosting_installWordPressV1

What does the hosting_installWordPressV1 tool do? +

Install WordPress on an existing website. The website must already exist before calling this endpoint. To create a new website first, use POST /api/hosting/v1/websites and poll GET /api/hosting/v1/websites until it appears. Call GET /api/hosting/v1/wordpress/installations filtered by username and domain before proceeding to check whether WordPress is already installed on the target domain/path. If WordPress already exists and overwrite is false (the default), the async job will fail. This operation is asynchronous: a successful response only means the install job has been queued, not that WordPress is ready. Installation typically takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered by username and domain to track progress. When the installation appears in that list, WordPress is ready. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does hosting_installWordPressV1 accept? +

hosting_installWordPressV1 accepts 10 parameters: domain, version, database, language, username, directory, overwrite, site_title, credentials, auto_updates. Required: domain, username, site_title, credentials. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_installWordPressV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_installWordPressV1: 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 hosting_installWordPressV1? +

hosting_installWordPressV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hosting_installWordPressV1? +

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

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

hosting_installWordPressV1 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →