hosting_startNode_jsBuildV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Destructive

Parameters 119 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-startnode-jsbuildv1.md

WHAT IT DOES

What hosting_startNode_jsBuildV1 does on Hostinger Api

AI agents call hosting_startNode_jsBuildV1 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
`app_type`	string	Yes	Node.js application type
`username`	string	Yes	username parameter
`entry_file`	string	—	The main entry point file for the application
`source_type`	string	Yes	The source type of the files
`build_script`	string	Yes	Build script that will be ran to build the application
`node_version`	integer	Yes	Node.js version
`root_directory`	string	Yes	Application root directory (where package.json is located) relative to public_html
`source_options`	object	Yes	Source-specific options
`package_manager`	string	—	Package manager
`output_directory`	string	Yes	Build output directory relative to the root directory

Parameters from the server's own tool schema.

RISK

Why hosting_startNode_jsBuildV1 is rated Critical

Irreversibly overwrites entire website contents; explicitly stated as undoable.

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

Risk signalsHigh parameter count (12 properties) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_startNode_jsBuildV1 Hidden

hosting_startNode_jsBuildV1 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_startNode_jsBuildV1"
  ]
}

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

FAQ

Questions about hosting_startNode_jsBuildV1

What does the hosting_startNode_jsBuildV1 tool do? +

Start a Node.js build process using files already present on the website's file storage. WARNING: on success this overwrites the website's existing contents and cannot be undone — verify this is intended before calling this endpoint. The source_type must be archive and source_options.archive_path must point to an existing archive file on the server (relative to the website document root). Use the Generate Upload URL endpoint to obtain credentials and upload the archive first. To auto-detect build settings from an archive before starting, first call the Get Node.js Build Settings from Archive endpoint. 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 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_startNode_jsBuildV1 accept? +

hosting_startNode_jsBuildV1 accepts 11 parameters: domain, app_type, username, entry_file, source_type, build_script, node_version, root_directory, source_options, package_manager, output_directory. Required: domain, app_type, username, source_type, build_script, node_version, root_directory, source_options, output_directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_startNode_jsBuildV1? +

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

hosting_startNode_jsBuildV1 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_startNode_jsBuildV1? +

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

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

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