New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

hosting_deploy_list_js

List JavaScript application deployments with their status. Use to check if deployment is pending, running, completed, or failed.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about hosting_deploy_list_js

What does the hosting_deploy_list_js tool do? +

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.

How do I enforce a policy on hosting_deploy_list_js? +

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.

What risk level is hosting_deploy_list_js? +

hosting_deploy_list_js is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hosting_deploy_list_js? +

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.

How do I block hosting_deploy_list_js completely? +

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.

What MCP server provides hosting_deploy_list_js? +

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.

// 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'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.