hosting_updatePHPVersionV1
Changes the PHP version of the website. Use the Get PHP details endpoint to see the versions available for the website.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-updatephpversionv1.md
What hosting_updatePHPVersionV1 does on Hostinger Api
AI agents invoke hosting_updatePHPVersionV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
version | string | Yes | PHP version to switch the website to. |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_updatePHPVersionV1 is rated High
Changing the PHP version of a live website triggers an external operational change that affects runtime behavior. It is not a simple data write — it reconfigures the execution environment, which can break applications if an incompatible version is selected. This falls under Execute due to its system-level operational effect, with high severity since misconfiguration can cause site-wide outages.
From the tool's definition Changes the PHP version of the website
Attacks that exploit this kind of access
The rule that runs hosting_updatePHPVersionV1 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_updatePHPVersionV1, this is the rule to start with:
hosting_updatePHPVersionV1 stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 hosting_updatePHPVersionV1 call is checked against it from then on.
Questions about hosting_updatePHPVersionV1
Changes the PHP version of the website. Use the Get PHP details endpoint to see the versions available for the website. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
hosting_updatePHPVersionV1 accepts 3 parameters: domain, version, username. Required: domain, version, 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_updatePHPVersionV1: 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_updatePHPVersionV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hosting_updatePHPVersionV1 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_updatePHPVersionV1. 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_updatePHPVersionV1 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.
Across the catalogue