agency_deploy_node_static
Deploy a node-static Agency Plan website from an archive. Uploads archive, triggers build, deploys to public_html. Operation is synchronous — site is live when tool returns.
This record as markdown: /tools/hostinger-mcp/agency-deploy-node-static.md
What agency_deploy_node_static does on Hostinger
AI agents invoke agency_deploy_node_static 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 agency_deploy_node_static is rated High
This tool runs a multi-step build and deployment process triggered by tool invocation. While it does not delete data (hence not Destructive) or transfer funds (hence not Financial), it executes code and external operations whose effects depend on the archive argument and environment. The build and deployment process constitutes code execution with side effects on a live production system.
From the tool's definition Tool "deploys to public_html", "triggers build", and "Operation is synchronous — site is live when tool returns." These phrases indicate the tool executes a deployment pipeline with external effects (building and live website activation).
Attacks that exploit this kind of access
The rule that runs agency_deploy_node_static 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 agency_deploy_node_static, this is the rule to start with:
agency_deploy_node_static 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 agency_deploy_node_static call is checked against it from then on.
Questions about agency_deploy_node_static
Deploy a node-static Agency Plan website from an archive. Uploads archive, triggers build, deploys to public_html. Operation is synchronous — site is live when tool returns. 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 agency_deploy_node_static: 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.
agency_deploy_node_static 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 agency_deploy_node_static 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 agency_deploy_node_static. 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.
agency_deploy_node_static 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