hosting_deploy_wp_import
Import a WordPress website from an archive and database dump. Files are extracted and site deployed automatically.
This record as markdown: /tools/hostinger-mcp/hosting-deploy-wp-import.md
What hosting_deploy_wp_import does on Hostinger
AI agents invoke hosting_deploy_wp_import 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.
Why hosting_deploy_wp_import is rated High
The tool executes a complex deployment operation with multiple side effects: extracting archives, importing database dumps, and deploying a WordPress installation. While not inherently destructive (the operation is theoretically reversible by deleting the deployed site), it triggers external operations whose effects depend entirely on the provided archive and dump arguments.
From the tool's definition "Import a WordPress website from an archive and database dump. Files are extracted and site deployed automatically." - This tool extracts files, deploys a site, and modifies hosting infrastructure automatically based on provided inputs.
Attacks that exploit this kind of access
The rule that runs hosting_deploy_wp_import 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 hosting_deploy_wp_import, this is the rule to start with:
hosting_deploy_wp_import 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, apply this rule, and every hosting_deploy_wp_import call is checked against it from then on.
Questions about hosting_deploy_wp_import
Import a WordPress website from an archive and database dump. Files are extracted and site deployed automatically. 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.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_deploy_wp_import: 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.
hosting_deploy_wp_import 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_deploy_wp_import 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_deploy_wp_import. 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_deploy_wp_import 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.
More on Hostinger, and thousands of servers like it.
Across the catalogue