hosting_deployStaticWebsite

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 32 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-deploystaticwebsite.md

WHAT IT DOES

What hosting_deployStaticWebsite does on Hostinger Api

AI agents invoke hosting_deployStaticWebsite 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 static website archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create ar
`removeArchive`	boolean	—	Whether to remove the archive file after successful deployment (default: false)

Parameters from the server's own tool schema.

RISK

Why hosting_deployStaticWebsite is rated High

This tool executes deployment operations that trigger external side effects on a hosting server. While not destructive (deployment is reversible via redeployment), it goes beyond simple read or write operations—it orchestrates a sequence of system-level actions (archive extraction, file movement, web server updates) whose effects depend on the provided archive content and domain parameters.

From the tool's definition Tool performs 'Deploy a static website from an archive file to a hosting server' with automatic extraction and deployment actions that trigger external operations (archive extraction, file placement on server, service deployment).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_deployStaticWebsite Rate-limited

hosting_deployStaticWebsite 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_deployStaticWebsite": {
      "limits": [
        {
          "counter": "hosting_deploystaticwebsite_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_deployStaticWebsite call is checked against it from then on.

FAQ

Questions about hosting_deployStaticWebsite

What does the hosting_deployStaticWebsite tool do? +

Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The archive will be extracted and deployed directly without any build steps. 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_deployStaticWebsite accept? +

hosting_deployStaticWebsite accepts 3 parameters: domain, archivePath, removeArchive. Required: domain, archivePath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_deployStaticWebsite? +

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

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

Can I rate-limit hosting_deployStaticWebsite? +

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

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

hosting_deployStaticWebsite 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 258 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 →