hosting_importWordpressWebsite
Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while ...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-importwordpresswebsite.md
What hosting_importWordpressWebsite does on Hostinger Api
AI agents use hosting_importWordpressWebsite to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name associated with the hosting account (e.g., example.com) |
archivePath | string | Yes | Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive f |
databaseDump | string | Yes | Absolute or relative path to a database dump file (.sql) |
Parameters from the server's own tool schema.
Why hosting_importWordpressWebsite is rated Medium
This tool uploads files and a database dump to a hosting server, deploying/overwriting a WordPress installation. While it could overwrite existing content, it is primarily a write/deploy operation rather than a pure deletion. The blast radius is high because it can overwrite existing website files and database content, but the operation is described as an import/deploy rather than an irreversible destructive action.
From the tool's definition Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website.
Attacks that exploit this kind of access
The rule that runs hosting_importWordpressWebsite 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_importWordpressWebsite, this is the rule to start with:
hosting_importWordpressWebsite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_importWordpressWebsite call is checked against it from then on.
Questions about hosting_importWordpressWebsite
Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. The username will be automatically resolved from the domain. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hosting_importWordpressWebsite accepts 3 parameters: domain, archivePath, databaseDump. Required: domain, archivePath, databaseDump. 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_importWordpressWebsite: 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_importWordpressWebsite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hosting_importWordpressWebsite 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_importWordpressWebsite. 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_importWordpressWebsite 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.
This server
Across the catalogue