hosting_replaceNode_jsEnvironmentVariablesV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 33 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-replacenode-jsenvironmentvariablesv1.md

WHAT IT DOES

What hosting_replaceNode_jsEnvironmentVariablesV1 does on Hostinger Api

AI agents use hosting_replaceNode_jsEnvironmentVariablesV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name
`env_vars`	array	Yes	Environment variables to set. This is the full desired set: any variable not in this list is deleted, and an empty array deletes every variable.
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_replaceNode_jsEnvironmentVariablesV1 is rated Medium

Modifies application configuration and restarts processes; reversible but causes service interruption and potential data loss.

From the tool's definition Replaces environment variables, deletes variables, restarts Node.js process.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_replaceNode_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_replaceNode_jsEnvironmentVariablesV1, this is the rule to start with:

hosting_replaceNode_jsEnvironmentVariablesV1 Rate-limited

hosting_replaceNode_jsEnvironmentVariablesV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_replaceNode_jsEnvironmentVariablesV1": {
      "limits": [
        {
          "counter": "hosting_replacenode_jsenvironmentvariablesv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_replaceNode_jsEnvironmentVariablesV1 call is checked against it from then on.

FAQ

Questions about hosting_replaceNode_jsEnvironmentVariablesV1

What does the hosting_replaceNode_jsEnvironmentVariablesV1 tool do? +

Replaces the website's Node.js environment variables with the ones provided. This is a full replace: any variable not in the request is deleted, and sending an empty env_vars array deletes every variable. Saving writes the values and restarts the running Node.js process. A restart is enough for apps that read environment variables at process start, such as Express or NestJS. It is not enough for frameworks that bake variables into the build. Next.js standalone is one of those: build-time values (including NEXT_PUBLIC_*) need a fresh build. After this call, use the Start Node.js build endpoint so those apps pick up the new values. The List Node.js environment variables endpoint returns masked values (), so never copy values from it into this request. Always send the full desired set with real values taken from the project .env file or the user prompt. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does hosting_replaceNode_jsEnvironmentVariablesV1 accept? +

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

How do I enforce a policy on hosting_replaceNode_jsEnvironmentVariablesV1? +

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

What risk level is hosting_replaceNode_jsEnvironmentVariablesV1? +

hosting_replaceNode_jsEnvironmentVariablesV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hosting_replaceNode_jsEnvironmentVariablesV1? +

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

How do I block hosting_replaceNode_jsEnvironmentVariablesV1 completely? +

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

What MCP server provides hosting_replaceNode_jsEnvironmentVariablesV1? +

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

KEEP EXPLORING

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

This server

All 382 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →