VPS_updatePostInstallScriptV1
Update a specific post-install script. Use this endpoint to modify existing automation scripts.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/vps-updatepostinstallscriptv1.md
What VPS_updatePostInstallScriptV1 does on Hostinger Api
AI agents use VPS_updatePostInstallScriptV1 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 |
|---|---|---|---|
name | string | Yes | Name of the script |
content | string | Yes | Content of the script |
postInstallScriptId | integer | Yes | Post-install script ID |
Parameters from the server's own tool schema.
Why VPS_updatePostInstallScriptV1 is rated Medium
This tool modifies post-install scripts on VPS infrastructure. While 'update' operations are Write-category (reversible), the severity is medium rather than low because misconfigured automation scripts could cause unintended system behavior, performance issues, or service disruption if an AI agent misuses this capability.
From the tool's definition Tool name contains 'update' and description states 'modify existing automation scripts', indicating reversible modification of data.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs VPS_updatePostInstallScriptV1 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 VPS_updatePostInstallScriptV1, this is the rule to start with:
VPS_updatePostInstallScriptV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every VPS_updatePostInstallScriptV1 call is checked against it from then on.
Questions about VPS_updatePostInstallScriptV1
Update a specific post-install script. Use this endpoint to modify existing automation scripts. 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.
VPS_updatePostInstallScriptV1 accepts 3 parameters: name, content, postInstallScriptId. Required: name, content, postInstallScriptId. 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 VPS_updatePostInstallScriptV1: 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.
VPS_updatePostInstallScriptV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the VPS_updatePostInstallScriptV1 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 VPS_updatePostInstallScriptV1. 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.
VPS_updatePostInstallScriptV1 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