agency_website_build_assets
Build Node.js assets for an Agency Plan website.
This record as markdown: /tools/hostinger-mcp/agency-website-build-assets.md
What agency_website_build_assets does on Hostinger
AI agents invoke agency_website_build_assets 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_website_build_assets is rated High
Building assets involves executing code compilation and transformation processes on the server. While not destructive by itself, build operations can have side effects (resource consumption, temporary file creation, potential build failures affecting deployments). The ability to trigger builds could be misused to consume resources or interfere with website deployment pipelines.
From the tool's definition Tool name contains 'build' and description states 'Build Node.js assets', indicating code compilation/execution. Context shows this is part of a hosting platform with deploy automation capabilities.
Attacks that exploit this kind of access
The rule that runs agency_website_build_assets 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_website_build_assets, this is the rule to start with:
agency_website_build_assets 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_website_build_assets call is checked against it from then on.
Questions about agency_website_build_assets
Build Node.js assets for an Agency Plan website. 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_website_build_assets: 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_website_build_assets 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_website_build_assets 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_website_build_assets. 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_website_build_assets 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