hosting_installWordPressThemeV1

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 63 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-installwordpressthemev1.md

WHAT IT DOES

What hosting_installWordPressThemeV1 does on Hostinger Api

AI agents invoke hosting_installWordPressThemeV1 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
`font`	string	—	Font identifier. Only applied when the theme is a Hostinger theme; the default is used when omitted.
`theme`	string	Yes	Slug of the theme to install. Hostinger theme slugs (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme) trigger the custom installer and forward the
`layout`	string	—	Layout identifier. Only applied when the theme is a Hostinger theme; the default is used when omitted.
`palette`	string	—	Palette identifier. Only applied when the theme is a Hostinger theme; the default is used when omitted.
`software`	string	Yes	WordPress installation (software) identifier
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_installWordPressThemeV1 is rated High

This tool triggers an external operation (installing a WordPress theme) on a live hosting environment. It is not simply writing data but executing an installation process on a remote server. Misuse could install malicious or unwanted themes on production WordPress sites, making severity high.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_installWordPressThemeV1 Rate-limited

hosting_installWordPressThemeV1 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_installWordPressThemeV1": {
      "limits": [
        {
          "counter": "hosting_installwordpressthemev1_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_installWordPressThemeV1 call is checked against it from then on.

FAQ

Questions about hosting_installWordPressThemeV1

What does the hosting_installWordPressThemeV1 tool do? +

Install a theme on an existing WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field). When the theme is one of the Hostinger themes (hostinger-blog, hostinger-affiliate-theme, hostinger-ai-theme), the optional palette, layout, and font fields are forwarded to the custom installer (defaults: palette1, layout1, default). For any other theme they are ignored. This operation is asynchronous: a successful response only means the install job has been queued, not that the theme 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_installWordPressThemeV1 accept? +

hosting_installWordPressThemeV1 accepts 6 parameters: font, theme, layout, palette, software, username. Required: theme, software, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_installWordPressThemeV1? +

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

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

Can I rate-limit hosting_installWordPressThemeV1? +

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

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

hosting_installWordPressThemeV1 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 →