hosting_patchNode_jsVulnerabilitiesV1

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-patchnode-jsvulnerabilitiesv1.md

WHAT IT DOES

What hosting_patchNode_jsVulnerabilitiesV1 does on Hostinger Api

AI agents use hosting_patchNode_jsVulnerabilitiesV1 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
`username`	string	Yes	username parameter
`vulnerability_ids`	array	Yes	List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint.

Parameters from the server's own tool schema.

RISK

Why hosting_patchNode_jsVulnerabilitiesV1 is rated Medium

An AI agent can call hosting_patchNode_jsVulnerabilitiesV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_patchNode_jsVulnerabilitiesV1 Rate-limited

hosting_patchNode_jsVulnerabilitiesV1 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_patchNode_jsVulnerabilitiesV1": {
      "limits": [
        {
          "counter": "hosting_patchnode_jsvulnerabilitiesv1_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_patchNode_jsVulnerabilitiesV1 call is checked against it from then on.

FAQ

Questions about hosting_patchNode_jsVulnerabilitiesV1

What does the hosting_patchNode_jsVulnerabilitiesV1 tool do? +

Patches the selected Node.js vulnerabilities by updating the affected package versions in package.json and opening a GitHub pull request in the connected repository. The customer reviews and merges the pull request; merging triggers the automatic deployment. Auto-fix is only available for websites deployed from a connected GitHub repository. Websites deployed from an archive have no auto-fix path and return a 404. The Hostinger GitHub App needs write access to the repository; without it the request fails with a 403 explaining the missing permission. Only vulnerabilities with is_patchable set to true can be patched. Non-patchable IDs in the selection are skipped; the pull request covers the patchable subset, listed in patched_vulnerability_ids. Selections without any patchable vulnerability are rejected with a 422. Only one patch pull request can be open at a time per website; close or merge it before patching again. Available on Business and Cloud Hosting plans. 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_patchNode_jsVulnerabilitiesV1 accept? +

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

How do I enforce a policy on hosting_patchNode_jsVulnerabilitiesV1? +

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

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

Can I rate-limit hosting_patchNode_jsVulnerabilitiesV1? +

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

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

hosting_patchNode_jsVulnerabilitiesV1 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 →

Across the catalogue

The MCP Attack Database →

Guides

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