agencyHosting_deployPhpApplication
Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and se...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agencyhosting-deployphpapplication.md
What agencyHosting_deployPhpApplication does on Hostinger Api
AI agents call agencyHosting_deployPhpApplication to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name of the Agency Plan website (e.g., example.com) |
archivePath | string | Yes | Absolute or relative path to the website archive file. Supported formats: zip, tar, tar.gz, tgz. If user provides a directory path, create an archive from it be |
removeArchive | boolean | — | Whether to remove the local archive file after successful deployment (default: true) |
Parameters from the server's own tool schema.
Why agencyHosting_deployPhpApplication is rated Critical
An AI agent that decides to call agencyHosting_deployPhpApplication doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hostinger Api is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs agencyHosting_deployPhpApplication 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 agencyHosting_deployPhpApplication, this is the rule to start with:
agencyHosting_deployPhpApplication is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every agencyHosting_deployPhpApplication call is checked against it from then on.
Questions about agencyHosting_deployPhpApplication
Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. For node-static websites that require a build step, use agencyHosting_deployNodeStaticWebsite instead. The website UID is automatically resolved from the domain. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
agencyHosting_deployPhpApplication accepts 3 parameters: domain, archivePath, removeArchive. Required: domain, archivePath. 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 agencyHosting_deployPhpApplication: 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.
agencyHosting_deployPhpApplication is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the agencyHosting_deployPhpApplication 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 agencyHosting_deployPhpApplication. 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.
agencyHosting_deployPhpApplication 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.
Across the catalogue