hosting_php_update_extensions
Enable/disable PHP extensions.
This record as markdown: /tools/hostinger-mcp/hosting-php-update-extensions.md
What hosting_php_update_extensions does on Hostinger
AI agents invoke hosting_php_update_extensions to trigger actions in Hostinger. 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.
Why hosting_php_update_extensions is rated High
Enabling or disabling PHP extensions changes the runtime environment of a web hosting account. This is an Execute-level action because it triggers changes to server configuration that affect how PHP processes requests. Misuse could break applications (disabling critical extensions) or introduce security risks (enabling dangerous extensions like `disable_functions` bypasses).
From the tool's definition Enable/disable PHP extensions
Attacks that exploit this kind of access
The rule that runs hosting_php_update_extensions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_php_update_extensions, this is the rule to start with:
hosting_php_update_extensions 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, apply this rule, and every hosting_php_update_extensions call is checked against it from then on.
Questions about hosting_php_update_extensions
Enable/disable PHP extensions. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_php_update_extensions: 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. Nothing to install.
hosting_php_update_extensions 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_php_update_extensions 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_php_update_extensions. 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_php_update_extensions is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
Across the catalogue