hosting_php_update_options
Update PHP options (ini settings).
This record as markdown: /tools/hostinger-mcp/hosting-php-update-options.md
What hosting_php_update_options does on Hostinger
AI agents use hosting_php_update_options to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why hosting_php_update_options is rated Medium
This tool modifies PHP configuration/ini settings on a hosting environment. It creates or modifies data reversibly (settings can be changed back), making it a Write operation. Misuse could cause application instability or security issues by altering PHP settings, but changes are generally reversible.
From the tool's definition Update PHP options (ini settings)
Attacks that exploit this kind of access
The rule that runs hosting_php_update_options 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_options, this is the rule to start with:
hosting_php_update_options 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, apply this rule, and every hosting_php_update_options call is checked against it from then on.
Questions about hosting_php_update_options
Update PHP options (ini settings). It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_php_update_options: 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_options 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 hosting_php_update_options 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_options. 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_options 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.
This server
Across the catalogue