This record as markdown: /tools/hostinger-mcp/hosting-nodejs-restart.md
What hosting_nodejs_restart does on Hostinger
AI agents invoke hosting_nodejs_restart to trigger actions in Hostinger. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why hosting_nodejs_restart is rated High
This tool executes a command to restart a Node.js application, which is an Execute category action (runs external operations whose effects depend on context). Severity is medium because restarting an application causes temporary downtime and service interruption but does not permanently destroy data or cause financial harm. Confidence is high because the description clearly indicates an operational trigger action.
From the tool's definition Tool description states 'Restart a Node.js application' — restart is an operational action that triggers external effects on a running process.
Attacks that exploit this kind of access
The rule that runs hosting_nodejs_restart 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_restart, this is the rule to start with:
hosting_nodejs_restart stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_restart call is checked against it from then on.
Questions about hosting_nodejs_restart
Restart a Node.js application. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_nodejs_restart: 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_restart is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hosting_nodejs_restart 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_restart. 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_restart 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.
Across the catalogue