agencyHosting_deployNodeStaticWebsite

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Destructive

Parameters 32 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/agencyhosting-deploynodestaticwebsite.md

WHAT IT DOES

What agencyHosting_deployNodeStaticWebsite does on Hostinger Api

AI agents call agencyHosting_deployNodeStaticWebsite 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 of the Agency Plan website (e.g., example.com)
`archivePath`	string	Yes	Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. The archive must contain the application source files. If user
`removeArchive`	boolean	—	Whether to remove the local archive file after successful deployment (default: true)

Parameters from the server's own tool schema.

RISK

Why agencyHosting_deployNodeStaticWebsite is rated Critical

An AI agent that decides to call agencyHosting_deployNodeStaticWebsite doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hostinger Api is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

agencyHosting_deployNodeStaticWebsite Hidden

agencyHosting_deployNodeStaticWebsite 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": [
    "agencyHosting_deployNodeStaticWebsite"
  ]
}

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

FAQ

Questions about agencyHosting_deployNodeStaticWebsite

What does the agencyHosting_deployNodeStaticWebsite tool do? +

Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For plain PHP applications that should be extracted as-is, use agencyHosting_deployPhpApplication instead. The website UID is automatically resolved from the domain. 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 agencyHosting_deployNodeStaticWebsite accept? +

agencyHosting_deployNodeStaticWebsite 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 agencyHosting_deployNodeStaticWebsite? +

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

agencyHosting_deployNodeStaticWebsite 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 agencyHosting_deployNodeStaticWebsite? +

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

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

agencyHosting_deployNodeStaticWebsite 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 → 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 →