hosting_listNode_jsEnvironmentVariablesV1
Lists the Node.js environment variables currently set for the website. Values are always masked as and cannot be read back through this API. Use this endpoint to see which keys are configured or to verify a change, not to read values. To change variables, use the Replace Node.js environment varia...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-listnode-jsenvironmentvariablesv1.md
What hosting_listNode_jsEnvironmentVariablesV1 does on Hostinger Api
AI agents call hosting_listNode_jsEnvironmentVariablesV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_listNode_jsEnvironmentVariablesV1 is rated Low
Retrieves configuration metadata only; actual secrets remain masked and inaccessible.
From the tool's definition Lists environment variables; values masked as ********; cannot read back
Attacks that exploit this kind of access
The rule that runs hosting_listNode_jsEnvironmentVariablesV1 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_listNode_jsEnvironmentVariablesV1, this is the rule to start with:
hosting_listNode_jsEnvironmentVariablesV1 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 Api, apply this rule, and every hosting_listNode_jsEnvironmentVariablesV1 call is checked against it from then on.
Questions about hosting_listNode_jsEnvironmentVariablesV1
Lists the Node.js environment variables currently set for the website. Values are always masked as and cannot be read back through this API. Use this endpoint to see which keys are configured or to verify a change, not to read values. To change variables, use the Replace Node.js environment variables endpoint. It replaces the whole set, so never copy the masked values from this response into that request; send the full desired set with real values taken from the project .env file or the user prompt instead. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_listNode_jsEnvironmentVariablesV1 accepts 2 parameters: domain, username. Required: domain, username. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_listNode_jsEnvironmentVariablesV1: 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.
hosting_listNode_jsEnvironmentVariablesV1 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_listNode_jsEnvironmentVariablesV1 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_listNode_jsEnvironmentVariablesV1. 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_listNode_jsEnvironmentVariablesV1 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.
This server
Across the catalogue