agency_deploy_php
Deploy a PHP application to an Agency Plan website from an archive. Extracts and serves as-is (no build step). Operation is synchronous.
This record as markdown: /tools/hostinger-mcp/agency-deploy-php.md
What agency_deploy_php does on Hostinger
AI agents invoke agency_deploy_php 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 agency_deploy_php is rated High
This tool executes a deployment operation that extracts and activates code on a live web server. While not irreversible (code can be redeployed), it qualifies as Execute rather than Write because it triggers external operations and code execution on infrastructure. The blast radius is high—a malicious actor could deploy compromised PHP code to a live website, impacting availability and security.
From the tool's definition Tool description states 'Deploy a PHP application to an Agency Plan website from an archive. Extracts and serves as-is (no build step).
Attacks that exploit this kind of access
The rule that runs agency_deploy_php 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 agency_deploy_php, this is the rule to start with:
agency_deploy_php 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 agency_deploy_php call is checked against it from then on.
Questions about agency_deploy_php
Deploy a PHP application to an Agency Plan website from an archive. Extracts and serves as-is (no build step). Operation is synchronous. 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 agency_deploy_php: 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.
agency_deploy_php 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 agency_deploy_php 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 agency_deploy_php. 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.
agency_deploy_php 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