mail_deleteForwarderV1
Delete a forwarder. The mailbox stops forwarding messages to the destination address immediately.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-deleteforwarderv1.md
What mail_deleteForwarderV1 does on Hostinger Api
AI agents call mail_deleteForwarderV1 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 |
|---|---|---|---|
forwarderId | string | Yes | Forwarder resource ID |
Parameters from the server's own tool schema.
Why mail_deleteForwarderV1 is rated Critical
Deleting a mail forwarder is a destructive action that permanently removes email forwarding configuration. The immediate and irreversible nature of stopping message forwarding, combined with the explicit 'delete' operation, places this in the Destructive category rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Delete a forwarder...The mailbox stops forwarding messages...immediately.' This is an irreversible deletion that cannot be undone.
Attacks that exploit this kind of access
The rule that runs mail_deleteForwarderV1 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 mail_deleteForwarderV1, this is the rule to start with:
mail_deleteForwarderV1 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 mail_deleteForwarderV1 call is checked against it from then on.
Questions about mail_deleteForwarderV1
Delete a forwarder. The mailbox stops forwarding messages to the destination address immediately. 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.
mail_deleteForwarderV1 accepts 1 parameter: forwarderId. Required: forwarderId. 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 mail_deleteForwarderV1: 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.
mail_deleteForwarderV1 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 mail_deleteForwarderV1 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 mail_deleteForwarderV1. 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.
mail_deleteForwarderV1 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