hosting_createNodeJSBuildFromArchiveV1
Upload a project archive, auto-detect build settings, and immediately start a Node.js build. This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website's file storage, build settings are auto-detected from the package.json inside the a...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-createnodejsbuildfromarchivev1.md
What hosting_createNodeJSBuildFromArchiveV1 does on Hostinger Api
AI agents invoke hosting_createNodeJSBuildFromArchiveV1 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 |
archive | string | Yes | Project archive file (.zip, .tar.gz, or .tgz), maximum 50MB |
app_type | string | — | Node.js application type override |
username | string | Yes | username parameter |
entry_file | string | — | Main entry point file override |
build_script | string | — | Build script override |
node_version | integer | — | Node.js version override (auto-detected from package.json if omitted) |
root_directory | string | — | Application root directory override (where package.json is located) relative to public_html |
package_manager | string | — | Package manager override |
output_directory | string | — | Build output directory override relative to the root directory |
Parameters from the server's own tool schema.
Why hosting_createNodeJSBuildFromArchiveV1 is rated High
This tool uploads code and immediately executes a build process on the hosting server. It triggers external operations (build execution) whose effects depend on the uploaded archive contents. This goes beyond a simple write/upload — it actively runs code on the server infrastructure, making it Execute category. Misuse could deploy malicious code or destabilize a hosted application, warranting high severity.
From the tool's definition 'Upload a project archive, auto-detect build settings, and immediately start a Node.js build' and 'the build process starts automatically'
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs hosting_createNodeJSBuildFromArchiveV1 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_createNodeJSBuildFromArchiveV1, this is the rule to start with:
hosting_createNodeJSBuildFromArchiveV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_createNodeJSBuildFromArchiveV1 call is checked against it from then on.
Questions about hosting_createNodeJSBuildFromArchiveV1
Upload a project archive, auto-detect build settings, and immediately start a Node.js build. This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website's file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB. Before archiving, exclude node_modules/ and any build output directories (e.g. dist/, .next/, build/) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit. Example (zip): zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*" The returned build uuid can be used to poll progress and retrieve logs via the Get Node.js Build Logs endpoint. 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.
hosting_createNodeJSBuildFromArchiveV1 accepts 10 parameters: domain, archive, app_type, username, entry_file, build_script, node_version, root_directory, package_manager, output_directory. Required: domain, archive, username. 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_createNodeJSBuildFromArchiveV1: 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_createNodeJSBuildFromArchiveV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hosting_createNodeJSBuildFromArchiveV1 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_createNodeJSBuildFromArchiveV1. 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_createNodeJSBuildFromArchiveV1 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.
Across the catalogue