hosting_updatePHPVersionV1

Changes the PHP version of the website. Use the Get PHP details endpoint to see the versions available for the website.

SERVERHostinger Api SOURCEhostinger-api-mcp
High RISK CLASS
Category Execute
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-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.

ParameterTypeRequiredDescription
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

Questions about hosting_updatePHPVersionV1

What does the hosting_updatePHPVersionV1 tool do? +

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.

What parameters does hosting_updatePHPVersionV1 accept? +

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.

How do I enforce a policy on hosting_updatePHPVersionV1? +

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.

What risk level is hosting_updatePHPVersionV1? +

hosting_updatePHPVersionV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hosting_updatePHPVersionV1? +

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.

How do I block hosting_updatePHPVersionV1 completely? +

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.

What MCP server provides hosting_updatePHPVersionV1? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.