hosting_updateNode_jsBuildSettingsV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 93 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-updatenode-jsbuildsettingsv1.md

WHAT IT DOES

What hosting_updateNode_jsBuildSettingsV1 does on Hostinger Api

AI agents use hosting_updateNode_jsBuildSettingsV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name
`app_type`	string	—	Node.js application framework. Set it explicitly when auto-detection picked the wrong one.
`username`	string	Yes	username parameter
`entry_file`	string	—	The main entry point file for the application (required for express, fastify, nest, nuxt and hono app types)
`build_script`	string	—	The package.json script that builds the application
`node_version`	integer	Yes	Node.js major version
`root_directory`	string	—	Application root directory (where package.json is located) relative to public_html. Omit it, or send ".", for public_html itself.
`package_manager`	string	—	Package manager used to install dependencies
`output_directory`	string	—	Build output directory relative to the root directory

Parameters from the server's own tool schema.

RISK

Why hosting_updateNode_jsBuildSettingsV1 is rated Medium

Modifies website build configuration reversibly; affects deployment but not data deletion.

From the tool's definition Replaces build settings; creates settings when none exist yet.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_updateNode_jsBuildSettingsV1 Rate-limited

hosting_updateNode_jsBuildSettingsV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_updateNode_jsBuildSettingsV1": {
      "limits": [
        {
          "counter": "hosting_updatenode_jsbuildsettingsv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about hosting_updateNode_jsBuildSettingsV1

What does the hosting_updateNode_jsBuildSettingsV1 tool do? +

Replaces the build settings stored for the website. Send the full set: node_version is required and every nullable field you omit is stored as null. Creates the settings when none exist yet. This does not start a build. Stored settings drive Git auto-deployment builds; a build started through the API uses the values sent in that request, so to rebuild with corrected settings call Start Node.js build with the same values. Typical fixes: a wrong app_type after auto-detection, or a missing entry_file for express, fastify, nest, nuxt and hono apps. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does hosting_updateNode_jsBuildSettingsV1 accept? +

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

How do I enforce a policy on hosting_updateNode_jsBuildSettingsV1? +

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

hosting_updateNode_jsBuildSettingsV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hosting_updateNode_jsBuildSettingsV1? +

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

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

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

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →