mail_aliases_list

List email aliases for an order.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What mail_aliases_list does on Hostinger

AI agents call mail_aliases_list to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mail_aliases_list is rated Low

The tool performs a list/query operation to retrieve email alias information associated with an order. It has no side effects—it neither creates, modifies, deletes, executes code, nor commits financial obligations. This is a straightforward data retrieval action with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'mail_aliases_list' and description 'List email aliases for an order' indicate a read-only operation that retrieves existing data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mail_aliases_list Allowed

mail_aliases_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_aliases_list": {}
  }
}

ALLOW ONLY 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_list call is checked against it from then on.

FAQ

Questions about mail_aliases_list

What does the mail_aliases_list tool do? +

List email aliases for an order. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mail_aliases_list? +

Register the Hostinger MCP server in PolicyLayer and add a rule for mail_aliases_list: 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_list? +

mail_aliases_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mail_aliases_list? +

Yes. Add a rate_limit block to the mail_aliases_list 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_list completely? +

Set action: deny in the PolicyLayer policy for mail_aliases_list. 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_list? +

mail_aliases_list 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 →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →