hosting_deployWordPressPluginV1

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 44 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-deploywordpresspluginv1.md

WHAT IT DOES

What hosting_deployWordPressPluginV1 does on Hostinger Api

AI agents invoke hosting_deployWordPressPluginV1 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	Slug of the plugin
`domain`	string	Yes	Domain name
`username`	string	Yes	username parameter
`plugin_path`	string	Yes	Relative path to the plugin directory from wp-content/plugins

Parameters from the server's own tool schema.

RISK

Why hosting_deployWordPressPluginV1 is rated High

Deploys and activates code on production WordPress sites; could execute arbitrary malicious plugins.

From the tool's definition Deploy a WordPress plugin, activated and made available.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_deployWordPressPluginV1 Rate-limited

hosting_deployWordPressPluginV1 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_deployWordPressPluginV1": {
      "limits": [
        {
          "counter": "hosting_deploywordpresspluginv1_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_deployWordPressPluginV1 call is checked against it from then on.

FAQ

Questions about hosting_deployWordPressPluginV1

What does the hosting_deployWordPressPluginV1 tool do? +

Deploy a WordPress plugin from an already uploaded directory. This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website's directory. The plugin will be activated and made available in the WordPress admin panel. 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_deployWordPressPluginV1 accept? +

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

How do I enforce a policy on hosting_deployWordPressPluginV1? +

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

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

Can I rate-limit hosting_deployWordPressPluginV1? +

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

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

hosting_deployWordPressPluginV1 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 382 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 →