hosting_deployJsApplication

SERVERHostinger Api SOURCEhostinger-api-mcp

High RISK CLASS

Category Execute

Parameters 32 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/hosting-deployjsapplication.md

WHAT IT DOES

What hosting_deployJsApplication does on Hostinger Api

AI agents invoke hosting_deployJsApplication 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.

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name associated with the hosting account (e.g., example.com)
`archivePath`	string	Yes	Absolute or relative path to the application archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archi
`removeArchive`	boolean	—	Whether to remove the archive file after successful deployment (default: false)

Parameters from the server's own tool schema.

RISK

Why hosting_deployJsApplication is rated High

This tool executes external operations (code deployment and automated build process) whose effects depend on the uploaded archive contents. While it creates/modifies application state on a hosting server, the primary risk is code execution on remote infrastructure triggered by the tool. This is Execute rather than Write because it actively runs build processes on the server, not merely storing data.

From the tool's definition Tool description states 'Deploy a JavaScript application from an archive file to a hosting server' and 'The build process will be triggered automatically on the server after the archive is uploaded.' This involves uploading code and triggering automated…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_deployJsApplication safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_deployJsApplication, this is the rule to start with:

hosting_deployJsApplication Rate-limited

hosting_deployJsApplication 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_deployJsApplication": {
      "limits": [
        {
          "counter": "hosting_deployjsapplication_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_deployJsApplication call is checked against it from then on.

FAQ

Questions about hosting_deployJsApplication

What does the hosting_deployJsApplication tool do? +

Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress. 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 hosting_deployJsApplication accept? +

hosting_deployJsApplication accepts 3 parameters: domain, archivePath, removeArchive. Required: domain, archivePath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_deployJsApplication? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_deployJsApplication: 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 hosting_deployJsApplication? +

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

Can I rate-limit hosting_deployJsApplication? +

Yes. Add a rate_limit block to the hosting_deployJsApplication 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 hosting_deployJsApplication completely? +

Set action: deny in the PolicyLayer policy for hosting_deployJsApplication. 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 hosting_deployJsApplication? +

hosting_deployJsApplication 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.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →