agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1

Builds and deploys a Node.js application for an Agency Plan website from an already-uploaded archive. Upload the archive to file browser first, then provide its relative path from document root in this request. Website contents are overwritten by the build result, which is deployed to public_html.

SERVERHostinger Api SOURCEhostinger-api-mcp
High RISK CLASS
Category Execute
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-buildagencyplanwebsitenodejsassetsv1.md

What agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 does on Hostinger Api

AI agents invoke agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 to trigger actions in Hostinger Api. 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.

ParameterTypeRequiredDescription
website_uid string Yes Agency Plan website UID
archive_path string Yes Directory, relative to the website document root, where the uploaded site archive currently lives. Most commonly this is simply `public_html`.

Parameters from the server's own tool schema.

Why agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 is rated High

agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAdmin/system-level operation

Questions about agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1

What does the agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 tool do? +

Builds and deploys a Node.js application for an Agency Plan website from an already-uploaded archive. Upload the archive to file browser first, then provide its relative path from document root in this request. Website contents are overwritten by the build result, which is deployed to public_html. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 accept? +

agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 accepts 2 parameters: website_uid, archive_path. Required: website_uid, archive_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1: 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.

What risk level is agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1? +

agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1? +

Yes. Add a rate_limit block to the agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 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.

How do I block agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 completely? +

Set action: deny in the PolicyLayer policy for agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1. 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.

What MCP server provides agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1? +

agency-hosting_buildAgencyPlanWebsiteNodeJSAssetsV1 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.