hosting_nodejs_builds_list
List Node.js builds for a website.
This record as markdown: /tools/hostinger-mcp/hosting-nodejs-builds-list.md
What hosting_nodejs_builds_list does on Hostinger
AI agents call hosting_nodejs_builds_list to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hosting_nodejs_builds_list is rated Low
This tool retrieves and displays existing Node.js build information without modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused by an AI agent—at worst, it would retrieve build metadata the agent should not access, but cannot cause infrastructure changes or data loss.
From the tool's definition Tool name and description indicate a list operation: 'hosting_nodejs_builds_list' with description 'List Node.js builds for a website.' The verb 'List' is explicitly a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs hosting_nodejs_builds_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_nodejs_builds_list, this is the rule to start with:
hosting_nodejs_builds_list 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, apply this rule, and every hosting_nodejs_builds_list call is checked against it from then on.
Questions about hosting_nodejs_builds_list
List Node.js builds for a website. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_nodejs_builds_list: 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. Nothing to install.
hosting_nodejs_builds_list 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_nodejs_builds_list 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_nodejs_builds_list. 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_nodejs_builds_list is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue