hosting_importWordpressWebsite

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 33 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-importwordpresswebsite.md

WHAT IT DOES

What hosting_importWordpressWebsite does on Hostinger Api

AI agents invoke hosting_importWordpressWebsite 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
`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.

RISK

Why hosting_importWordpressWebsite is rated High

Tool triggers a full deployment pipeline, extracting archives and configuring a live site server-side.

From the tool's definition imports archive, uploads files, deploys complete WordPress website end-to-end

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

hosting_importWordpressWebsite 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_importWordpressWebsite": {
      "limits": [
        {
          "counter": "hosting_importwordpresswebsite_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_importWordpressWebsite call is checked against it from then on.

FAQ

Questions about hosting_importWordpressWebsite

What does the hosting_importWordpressWebsite tool do? +

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. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end. The username will be automatically resolved from the domain. 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_importWordpressWebsite accept? +

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.

How do I enforce a policy on hosting_importWordpressWebsite? +

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.

What risk level is hosting_importWordpressWebsite? +

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

Can I rate-limit hosting_importWordpressWebsite? +

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.

How do I block hosting_importWordpressWebsite completely? +

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.

What MCP server provides hosting_importWordpressWebsite? +

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.

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 →