This record as markdown: /tools/hostinger-mcp/mail-catchalls-list.md
What mail_catchalls_list does on Hostinger
AI agents call mail_catchalls_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.
Why mail_catchalls_list is rated Low
The tool retrieves and displays existing catch-all email configurations without modifying, creating, or deleting any data. This is a standard read operation with minimal risk if misused by an AI agent—it only exposes information about email routing rules.
From the tool's definition Tool name and description indicate a list operation ('List catch-all configurations'). This is a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs mail_catchalls_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_catchalls_list, this is the rule to start with:
mail_catchalls_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every mail_catchalls_list call is checked against it from then on.
Questions about mail_catchalls_list
List catch-all configurations. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for mail_catchalls_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.
mail_catchalls_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mail_catchalls_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.
Set action: deny in the PolicyLayer policy for mail_catchalls_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.
mail_catchalls_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.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue