domains_deleteDomainForwardingV1
Delete domain forwarding data. Use this endpoint to remove redirect configuration from domains.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-deletedomainforwardingv1.md
What domains_deleteDomainForwardingV1 does on Hostinger Api
AI agents call domains_deleteDomainForwardingV1 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 |
Parameters from the server's own tool schema.
Why domains_deleteDomainForwardingV1 is rated Critical
This tool performs an irreversible delete operation that removes domain forwarding/redirect configurations. Once deleted, the forwarding rules are permanently removed and cannot be recovered without reconfiguring them manually. This fits the Destructive category as it involves permanent data removal.
From the tool's definition Tool name 'deleteDomainForwarding' and description 'Delete domain forwarding data' and 'remove redirect configuration from domains' indicate irreversible deletion of domain forwarding configuration.
Attacks that exploit this kind of access
The rule that runs domains_deleteDomainForwardingV1 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 domains_deleteDomainForwardingV1, this is the rule to start with:
domains_deleteDomainForwardingV1 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 domains_deleteDomainForwardingV1 call is checked against it from then on.
Questions about domains_deleteDomainForwardingV1
Delete domain forwarding data. Use this endpoint to remove redirect configuration from domains. 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.
domains_deleteDomainForwardingV1 accepts 1 parameter: domain. Required: domain. 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 domains_deleteDomainForwardingV1: 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.
domains_deleteDomainForwardingV1 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 domains_deleteDomainForwardingV1 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 domains_deleteDomainForwardingV1. 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.
domains_deleteDomainForwardingV1 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