# 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.

Agent View of the PolicyLayer registry record for `agencyHosting_deployPhpApplication`. HTML page: https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agencyhosting-deployphpapplication

## Facts

- Tool: `agencyHosting_deployPhpApplication`
- Server: Hostinger Api (`hostinger-api-mcp`) — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp.md
- Install: `npx -y hostinger-api-mcp`
- Homepage: https://github.com/hostinger/api-mcp-server
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| 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 | no | Whether to remove the local archive file after successful deployment (default: true) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "agencyHosting_deployPhpApplication",
    "arguments": {
      "domain": "<domain>",
      "archivePath": "<archivePath>"
    }
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hostinger Api:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "agencyHosting_deployPhpApplication"
  ]
}
```

## Other tools on Hostinger Api (257)

- `agency-hosting_clearAgencyPlanWebsiteCacheV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-clearagencyplanwebsitecachev1.md
- `agency-hosting_deleteAgencyPlanWebsiteCronJobV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitecronjobv1.md
- `agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitedatabaseuserv1.md
- `agency-hosting_deleteAgencyPlanWebsiteDatabaseV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitedatabasev1.md
- `agency-hosting_deleteAgencyPlanWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitev1.md
- `agencyHosting_deployNodeStaticWebsite` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agencyhosting-deploynodestaticwebsite.md
- `billing_deletePaymentMethodV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/billing-deletepaymentmethodv1.md
- `DNS_deleteDNSRecordsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/dns-deletednsrecordsv1.md
- `DNS_resetDNSRecordsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/dns-resetdnsrecordsv1.md
- `domains_deleteDomainForwardingV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-deletedomainforwardingv1.md
- `domains_deleteWHOISProfileV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-deletewhoisprofilev1.md
- `ecommerce_deleteStoreV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/ecommerce-deletestorev1.md
- `hosting_clearWebsiteCacheV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-clearwebsitecachev1.md
- `hosting_deleteAccountCronJobV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountcronjobv1.md
- `hosting_deleteAccountDatabaseRemoteConnectionV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountdatabaseremoteconnectionv1.md
- `hosting_deleteAccountDatabaseV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountdatabasev1.md
- `hosting_deleteWebsiteParkedDomainV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsiteparkeddomainv1.md
- `hosting_deleteWebsiteSubdomainV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsitesubdomainv1.md
- `hosting_deleteWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsitev1.md
- `hosting_deleteWordPressInstallationV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewordpressinstallationv1.md
- `hosting_uninstallWordPressPluginsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-uninstallwordpresspluginsv1.md
- `hosting_uninstallWordPressThemesV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-uninstallwordpressthemesv1.md
- `mail_deleteMailboxV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/mail-deletemailboxv1.md
- `mail_deleteWebhookV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/mail-deletewebhookv1.md
- `mail_revokeAPITokenV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/mail-revokeapitokenv1.md
- `reach_deleteAContactV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/reach-deleteacontactv1.md
- `VPS_deleteFirewallRuleV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deletefirewallrulev1.md
- `VPS_deleteFirewallV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deletefirewallv1.md
- `VPS_deletePostInstallScriptV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deletepostinstallscriptv1.md
- `VPS_deleteProjectV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/vps-deleteprojectv1.md
- …and 227 more: https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-hostinger-hostinger-api-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-hostinger-hostinger-api-mcp