hosting_deploy_list_js
List JavaScript application deployments with their status. Use to check if deployment is pending, running, completed, or failed.
This record as markdown: /tools/hostinger-mcp/hosting-deploy-list-js.md
What hosting_deploy_list_js does on Hostinger
AI agents call hosting_deploy_list_js to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hosting_deploy_list_js is rated Low
This tool only lists and queries deployment records and their statuses. It does not trigger, modify, or delete any deployments. It is a read-only operation with minimal blast radius.
From the tool's definition 'List JavaScript application deployments with their status' and 'Use to check if deployment is pending, running, completed, or failed' — purely retrieves and displays deployment status information
Attacks that exploit this kind of access
The rule that runs hosting_deploy_list_js 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_deploy_list_js, this is the rule to start with:
hosting_deploy_list_js is read-only, so it stays allowed. 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_deploy_list_js call is checked against it from then on.
Questions about hosting_deploy_list_js
List JavaScript application deployments with their status. Use to check if deployment is pending, running, completed, or failed. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_deploy_list_js: 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_deploy_list_js is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hosting_deploy_list_js 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_deploy_list_js. 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_deploy_list_js 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.
This server
Across the catalogue