hosting_getNode_jsBuildSettingsV1
Returns the build settings stored for the website: framework (app_type), Node.js version, root and output directory, build script, entry file and package manager. Stored settings drive Git auto-deployment builds. A build started through the API uses the values sent in that request and saves them ...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-getnode-jsbuildsettingsv1.md
What hosting_getNode_jsBuildSettingsV1 does on Hostinger Api
AI agents call hosting_getNode_jsBuildSettingsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_getNode_jsBuildSettingsV1 is rated Low
Tool retrieves configuration data without modifying or executing operations.
From the tool's definition Returns build settings; stored for website framework, Node.js version, root directory
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs hosting_getNode_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_getNode_jsBuildSettingsV1, this is the rule to start with:
hosting_getNode_jsBuildSettingsV1 is read-only, so it stays allowed. 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_getNode_jsBuildSettingsV1 call is checked against it from then on.
Questions about hosting_getNode_jsBuildSettingsV1
Returns the build settings stored for the website: framework (app_type), Node.js version, root and output directory, build script, entry file and package manager. Stored settings drive Git auto-deployment builds. A build started through the API uses the values sent in that request and saves them here only when no settings exist yet. Returns 404 until the first build or the first settings update stores them. Use this after a failed build to check whether the framework or the entry file were detected wrong, then fix them with the Update Node.js build settings endpoint. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_getNode_jsBuildSettingsV1 accepts 2 parameters: domain, username. Required: domain, 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_getNode_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.
hosting_getNode_jsBuildSettingsV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hosting_getNode_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.
Set action: deny in the PolicyLayer policy for hosting_getNode_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.
hosting_getNode_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.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue