hosting_deployWordpressTheme

Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment.

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 43 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-deploywordpresstheme.md

WHAT IT DOES

What hosting_deployWordpressTheme does on Hostinger Api

AI agents invoke hosting_deployWordpressTheme 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
`slug`	string	Yes	WordPress theme slug (e.g., twentytwentyfive)
`domain`	string	Yes	Domain name associated with the hosting account (e.g., example.com)
`activate`	boolean	—	Whether to activate the theme after deployment (default: false)
`themePath`	string	Yes	Absolute or relative path to the theme directory containing all theme files

Parameters from the server's own tool schema.

RISK

Why hosting_deployWordpressTheme is rated High

Uploading files to a server and triggering deployment execution qualifies as Execute rather than Write, because it involves triggering external operations on infrastructure (a hosting server) whose side effects extend beyond simple data storage. While reversible if the theme can be undeployed, the execution of deployment logic and the potential to activate/deactivate themes makes this Execute-category.

From the tool's definition Tool description states it 'uploads all theme files and triggers theme deployment' with optional activation. The verb 'triggers' indicates execution of external operations (deployment process) whose effects depend on arguments (which theme, activation flag).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_deployWordpressTheme Rate-limited

hosting_deployWordpressTheme 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_deployWordpressTheme": {
      "limits": [
        {
          "counter": "hosting_deploywordpresstheme_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_deployWordpressTheme call is checked against it from then on.

FAQ

Questions about hosting_deployWordpressTheme

What does the hosting_deployWordpressTheme tool do? +

Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment. 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_deployWordpressTheme accept? +

hosting_deployWordpressTheme accepts 4 parameters: slug, domain, activate, themePath. Required: slug, domain, themePath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_deployWordpressTheme? +

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

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

Can I rate-limit hosting_deployWordpressTheme? +

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

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

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