hosting_analyseFailedNode_jsBuildV1
Returns an AI analysis of why a build failed and how to fix it, based on the build logs, the project file list and package.json. Only builds in the failed state can be analysed; any other state returns 422. When no analysis could be produced both analysis and solution are null, in which case read...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-analysefailednode-jsbuildv1.md
What hosting_analyseFailedNode_jsBuildV1 does on Hostinger Api
AI agents call hosting_analyseFailedNode_jsBuildV1 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_analyseFailedNode_jsBuildV1 is rated Low
Tool analyzes and returns diagnostic information about failed builds without modifying data.
From the tool's definition Returns AI analysis of build logs, project files, package.json. Read-only diagnostic output.
Attacks that exploit this kind of access
The rule that runs hosting_analyseFailedNode_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_analyseFailedNode_jsBuildV1, this is the rule to start with:
hosting_analyseFailedNode_jsBuildV1 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_analyseFailedNode_jsBuildV1 call is checked against it from then on.
Questions about hosting_analyseFailedNode_jsBuildV1
Returns an AI analysis of why a build failed and how to fix it, based on the build logs, the project file list and package.json. Only builds in the failed state can be analysed; any other state returns 422. When no analysis could be produced both analysis and solution are null, in which case read Get NodeJS build logs instead. Each call runs the analysis again, so call it once per failed build and keep the result. Limited to 5 calls per minute per API client (429 above that). It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_analyseFailedNode_jsBuildV1 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_analyseFailedNode_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.
hosting_analyseFailedNode_jsBuildV1 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_analyseFailedNode_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.
Set action: deny in the PolicyLayer policy for hosting_analyseFailedNode_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.
hosting_analyseFailedNode_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.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue