mail_aliases_delete

Delete an email alias.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/mail-aliases-delete.md

WHAT IT DOES

What mail_aliases_delete does on Hostinger

AI agents call mail_aliases_delete 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.

RISK

Why mail_aliases_delete is rated Critical

Deleting an email alias cannot be undone and permanently removes email routing/forwarding functionality for that alias. This falls into the Destructive category (irreversible deletion). Severity is high because loss of email aliases can disrupt communication workflows, though it does not involve financial loss or code execution. Confidence is very high given explicit 'delete' language in both name and description.

From the tool's definition Tool name contains 'delete' and description states 'Delete an email alias' — this is an irreversible removal of email configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mail_aliases_delete 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 mail_aliases_delete, this is the rule to start with:

mail_aliases_delete Hidden

mail_aliases_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "mail_aliases_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every mail_aliases_delete call is checked against it from then on.

FAQ

Questions about mail_aliases_delete

What does the mail_aliases_delete tool do? +

Delete an email alias. 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.

How do I enforce a policy on mail_aliases_delete? +

Register the Hostinger MCP server in PolicyLayer and add a rule for mail_aliases_delete: 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.

What risk level is mail_aliases_delete? +

mail_aliases_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mail_aliases_delete? +

Yes. Add a rate_limit block to the mail_aliases_delete 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.

How do I block mail_aliases_delete completely? +

Set action: deny in the PolicyLayer policy for mail_aliases_delete. 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.

What MCP server provides mail_aliases_delete? +

mail_aliases_delete 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.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →