hosting_deployStaticSiteArchiveV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Destructive

Parameters 33 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-deploystaticsitearchivev1.md

WHAT IT DOES

What hosting_deployStaticSiteArchiveV1 does on Hostinger Api

AI agents call hosting_deployStaticSiteArchiveV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name
`username`	string	Yes	username parameter
`archive_path`	string	Yes	Relative path to the archive file from website root directory

Parameters from the server's own tool schema.

RISK

Why hosting_deployStaticSiteArchiveV1 is rated Critical

Irreversibly replaces entire website content with archive; no recovery mechanism available.

From the tool's definition overwrites website's existing contents and cannot be undone

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_deployStaticSiteArchiveV1 Hidden

hosting_deployStaticSiteArchiveV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "hosting_deployStaticSiteArchiveV1"
  ]
}

RESTRICT 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_deployStaticSiteArchiveV1 call is checked against it from then on.

FAQ

Questions about hosting_deployStaticSiteArchiveV1

What does the hosting_deployStaticSiteArchiveV1 tool do? +

Deploy a static application from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — verify this is intended before calling this endpoint. This endpoint allows you to deploy a static application from an archive file that has been uploaded to the website's directory. This only works for static sites (pre-built HTML/CSS/JS with no build step). For Node.js applications, use Create NodeJS build from archive instead, or Start Node.js build if the archive is already uploaded. For WordPress sites, use Import WordPress website. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does hosting_deployStaticSiteArchiveV1 accept? +

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

How do I enforce a policy on hosting_deployStaticSiteArchiveV1? +

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

hosting_deployStaticSiteArchiveV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hosting_deployStaticSiteArchiveV1? +

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

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

hosting_deployStaticSiteArchiveV1 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →