wp_install

Install WordPress on a hosting account.

SERVERHostinger SOURCEidugeni/hostinger-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/wp-install.md

WHAT IT DOES

What wp_install does on Hostinger

AI agents invoke wp_install to trigger actions in Hostinger. 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.

RISK

Why wp_install is rated High

Installing WordPress triggers an external operation that provisions software, creates files, configures databases, and sets up a web application on a hosting account. This goes beyond a simple write — it executes a multi-step deployment process with broad side effects. Misuse could install WordPress on the wrong account or with insecure credentials, making it high severity.

From the tool's definition Install WordPress on a hosting account

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_install safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_install, this is the rule to start with:

wp_install Rate-limited

wp_install 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": {
    "wp_install": {
      "limits": [
        {
          "counter": "wp_install_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, apply this rule, and every wp_install call is checked against it from then on.

FAQ

Questions about wp_install

What does the wp_install tool do? +

Install WordPress on a hosting account. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wp_install? +

Register the Hostinger MCP server in PolicyLayer and add a rule for wp_install: 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. Nothing to install.

What risk level is wp_install? +

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

Can I rate-limit wp_install? +

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

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

wp_install is provided by the Hostinger MCP server (idugeni/hostinger-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, and thousands of servers like it.

This server

All 284 Hostinger 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 →