This record as markdown: /tools/hostinger-mcp/domains-delete-forwarding.md
What domains_delete_forwarding does on Hostinger
AI agents call domains_delete_forwarding to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why domains_delete_forwarding is rated Critical
The tool permanently removes domain forwarding configuration. Once deleted, the forwarding rules are gone and must be manually recreated. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While not as severe as account deletion, removing domain forwarding can break email routing or web traffic redirection, making it high severity for a domain…
From the tool's definition Tool name contains 'delete' and description states 'Remove domain forwarding' — this is an irreversible deletion operation that cannot be undone without manual reconfiguration.
Attacks that exploit this kind of access
The rule that runs domains_delete_forwarding 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 domains_delete_forwarding, this is the rule to start with:
domains_delete_forwarding 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, apply this rule, and every domains_delete_forwarding call is checked against it from then on.
Questions about domains_delete_forwarding
Remove domain forwarding. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for domains_delete_forwarding: 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.
domains_delete_forwarding 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_delete_forwarding 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_delete_forwarding. 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_delete_forwarding 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