hosting_resetPHPExtensionsV1
Resets all PHP extensions of the website to their default state. Use it to recover from extension conflicts or restore the original configuration.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-resetphpextensionsv1.md
What hosting_resetPHPExtensionsV1 does on Hostinger Api
AI agents use hosting_resetPHPExtensionsV1 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 |
|---|---|---|---|
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_resetPHPExtensionsV1 is rated Medium
This tool modifies the PHP configuration by resetting extensions to defaults. While it overwrites current settings, it's restoring a known default state rather than deleting data, making it a Write operation. It's reversible in the sense that extensions can be reconfigured, but misuse could disrupt a running website by removing custom PHP extension configurations.
From the tool's definition Resets all PHP extensions of the website to their default state
Attacks that exploit this kind of access
The rule that runs hosting_resetPHPExtensionsV1 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_resetPHPExtensionsV1, this is the rule to start with:
hosting_resetPHPExtensionsV1 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 hosting_resetPHPExtensionsV1 call is checked against it from then on.
Questions about hosting_resetPHPExtensionsV1
Resets all PHP extensions of the website to their default state. Use it to recover from extension conflicts or restore the original configuration. 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.
hosting_resetPHPExtensionsV1 accepts 2 parameters: domain, username. Required: domain, 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_resetPHPExtensionsV1: 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_resetPHPExtensionsV1 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_resetPHPExtensionsV1 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_resetPHPExtensionsV1. 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_resetPHPExtensionsV1 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