mail_deleteCatchAllV1
Delete a catch-all. Messages sent to unknown addresses of the domain are no longer routed to the mailbox.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-deletecatchallv1.md
What mail_deleteCatchAllV1 does on Hostinger Api
AI agents call mail_deleteCatchAllV1 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 |
|---|---|---|---|
catchallId | string | Yes | Catch-all resource ID |
Parameters from the server's own tool schema.
Why mail_deleteCatchAllV1 is rated Critical
This tool irreversibly deletes email infrastructure configuration (catch-all routing). Once deleted, email messages sent to unknown addresses will no longer be routed to the configured mailbox, breaking email delivery for those addresses. This is a destructive operation that cannot be automatically reversed.
From the tool's definition Tool name contains 'delete' and description states 'Delete a catch-all' — this irreversibly removes an email routing rule. The action cannot be undone without manual reconfiguration.
Attacks that exploit this kind of access
The rule that runs mail_deleteCatchAllV1 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_deleteCatchAllV1, this is the rule to start with:
mail_deleteCatchAllV1 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_deleteCatchAllV1 call is checked against it from then on.
Questions about mail_deleteCatchAllV1
Delete a catch-all. Messages sent to unknown addresses of the domain are no longer routed to the mailbox. 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_deleteCatchAllV1 accepts 1 parameter: catchallId. Required: catchallId. 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_deleteCatchAllV1: 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_deleteCatchAllV1 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_deleteCatchAllV1 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_deleteCatchAllV1. 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_deleteCatchAllV1 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