hosting_getNode_jsBuildDetailsV1
Returns one build by UUID: its state (pending, running, completed, failed), the options it ran with and timestamps. Poll this while a build is pending or running. When it is failed, read Get NodeJS build logs and Analyse failed Node.js build for the cause. Returns 404 when the UUID does not belon...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-getnode-jsbuilddetailsv1.md
What hosting_getNode_jsBuildDetailsV1 does on Hostinger Api
AI agents call hosting_getNode_jsBuildDetailsV1 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 |
|---|---|---|---|
uuid | string | Yes | Build UUID |
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_getNode_jsBuildDetailsV1 is rated Low
Tool retrieves build status and metadata without modifying or executing any operations.
From the tool's definition Returns one build by UUID: its state, options, timestamps. Poll this while pending or running.
Attacks that exploit this kind of access
The rule that runs hosting_getNode_jsBuildDetailsV1 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_jsBuildDetailsV1, this is the rule to start with:
hosting_getNode_jsBuildDetailsV1 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_jsBuildDetailsV1 call is checked against it from then on.
Questions about hosting_getNode_jsBuildDetailsV1
Returns one build by UUID: its state (pending, running, completed, failed), the options it ran with and timestamps. Poll this while a build is pending or running. When it is failed, read Get NodeJS build logs and Analyse failed Node.js build for the cause. Returns 404 when the UUID does not belong to a build of this website. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_getNode_jsBuildDetailsV1 accepts 3 parameters: uuid, domain, username. Required: uuid, 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_jsBuildDetailsV1: 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_jsBuildDetailsV1 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_jsBuildDetailsV1 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_jsBuildDetailsV1. 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_jsBuildDetailsV1 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