hosting_getPHPDetailsV1
Returns the full PHP configuration for the website: current version, available versions (supported and unsupported), enabled/disabled extensions, options with their current value, default, type and the plan limit (max), and conflicting extension groups. Use it to check the current PHP setup befor...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-getphpdetailsv1.md
What hosting_getPHPDetailsV1 does on Hostinger Api
AI agents call hosting_getPHPDetailsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_getPHPDetailsV1 is rated Low
This is a straightforward read operation that queries and retrieves configuration details. It provides information needed for decision-making but performs no modifications, deletions, or code execution. The blast radius of misuse is minimal—an agent could retrieve unnecessary configuration details but cannot cause harm through this tool alone.
From the tool's definition Tool returns/retrieves PHP configuration data. Description explicitly states it "Returns the full PHP configuration" and is used "to check the current PHP setup" before making changes.
Attacks that exploit this kind of access
The rule that runs hosting_getPHPDetailsV1 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_getPHPDetailsV1, this is the rule to start with:
hosting_getPHPDetailsV1 is read-only, so it stays allowed. 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_getPHPDetailsV1 call is checked against it from then on.
Questions about hosting_getPHPDetailsV1
Returns the full PHP configuration for the website: current version, available versions (supported and unsupported), enabled/disabled extensions, options with their current value, default, type and the plan limit (max), and conflicting extension groups. Use it to check the current PHP setup before updating the version, extensions or options. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_getPHPDetailsV1 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_getPHPDetailsV1: 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_getPHPDetailsV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hosting_getPHPDetailsV1 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_getPHPDetailsV1. 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_getPHPDetailsV1 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