hosting_deployWordpressPlugin
Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-deploywordpressplugin.md
What hosting_deployWordpressPlugin does on Hostinger Api
AI agents invoke hosting_deployWordpressPlugin 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 plugin slug (e.g., omnisend) |
domain | string | Yes | Domain name associated with the hosting account (e.g., example.com) |
pluginPath | string | Yes | Absolute or relative path to the plugin directory containing all plugin files |
Parameters from the server's own tool schema.
Why hosting_deployWordpressPlugin is rated High
Although the tool performs file uploads (Write operation), the primary action is 'triggers plugin deployment' — an automated execution of code/operations on a remote server. The severity is medium because while code execution occurs, it is scoped to a specific WordPress plugin deployment context rather than arbitrary command execution, and the blast radius is limited compared to unrestricted shell access.
From the tool's definition The tool 'uploads all plugin files and triggers plugin deployment' to a hosting server. This involves executing deployment operations whose effects depend on which plugin files are supplied.
Attacks that exploit this kind of access
The rule that runs hosting_deployWordpressPlugin 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_deployWordpressPlugin, this is the rule to start with:
hosting_deployWordpressPlugin 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_deployWordpressPlugin call is checked against it from then on.
Questions about hosting_deployWordpressPlugin
Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin 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.
hosting_deployWordpressPlugin accepts 3 parameters: slug, domain, pluginPath. Required: slug, domain, pluginPath. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_deployWordpressPlugin: 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.
hosting_deployWordpressPlugin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hosting_deployWordpressPlugin 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.
Set action: deny in the PolicyLayer policy for hosting_deployWordpressPlugin. 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.
hosting_deployWordpressPlugin 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.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue