mail_deleteWebhookV1
Permanently delete a webhook. This action cannot be undone. After deletion the URL no longer receives event notifications.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-deletewebhookv1.md
What mail_deleteWebhookV1 does on Hostinger Api
AI agents call mail_deleteWebhookV1 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 |
|---|---|---|---|
webhookId | string | Yes | Webhook ID (returned when the webhook was created) |
Parameters from the server's own tool schema.
Why mail_deleteWebhookV1 is rated Critical
An AI agent that decides to call mail_deleteWebhookV1 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.
Attacks that exploit this kind of access
The rule that runs mail_deleteWebhookV1 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_deleteWebhookV1, this is the rule to start with:
mail_deleteWebhookV1 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_deleteWebhookV1 call is checked against it from then on.
Questions about mail_deleteWebhookV1
Permanently delete a webhook. This action cannot be undone. After deletion the URL no longer receives event notifications. 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_deleteWebhookV1 accepts 1 parameter: webhookId. Required: webhookId. 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_deleteWebhookV1: 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_deleteWebhookV1 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_deleteWebhookV1 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_deleteWebhookV1. 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_deleteWebhookV1 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