hosting_deleteWebsiteParkedDomainV1
Delete an existing parked or alias domain from the selected website. Use this endpoint to remove parked domains that are no longer needed.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsiteparkeddomainv1.md
What hosting_deleteWebsiteParkedDomainV1 does on Hostinger Api
AI agents call hosting_deleteWebsiteParkedDomainV1 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 |
username | string | Yes | username parameter |
parkedDomain | string | Yes | parkedDomain parameter |
Parameters from the server's own tool schema.
Why hosting_deleteWebsiteParkedDomainV1 is rated Critical
This tool permanently deletes a domain alias/parked domain from a website. Domain configurations cannot be recovered once deleted without manual re-creation. This is an irreversible destructive action affecting website infrastructure. While not directly financial, the impact is severe as it could break website functionality or DNS routing if misused by an agent.
From the tool's definition Tool name contains 'delete' and description states 'Delete an existing parked or alias domain' and 'remove parked domains' — irreversible removal of domain configuration data.
Attacks that exploit this kind of access
The rule that runs hosting_deleteWebsiteParkedDomainV1 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_deleteWebsiteParkedDomainV1, this is the rule to start with:
hosting_deleteWebsiteParkedDomainV1 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 hosting_deleteWebsiteParkedDomainV1 call is checked against it from then on.
Questions about hosting_deleteWebsiteParkedDomainV1
Delete an existing parked or alias domain from the selected website. Use this endpoint to remove parked domains that are no longer needed. 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.
hosting_deleteWebsiteParkedDomainV1 accepts 3 parameters: domain, username, parkedDomain. Required: domain, username, parkedDomain. 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_deleteWebsiteParkedDomainV1: 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_deleteWebsiteParkedDomainV1 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 hosting_deleteWebsiteParkedDomainV1 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_deleteWebsiteParkedDomainV1. 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_deleteWebsiteParkedDomainV1 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