This record as markdown: /tools/hostinger-mcp/mail-autoreplies-delete.md
What mail_autoreplies_delete does on Hostinger
AI agents call mail_autoreplies_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.
Why mail_autoreplies_delete is rated Critical
This tool permanently removes autoreply settings, which cannot be undone without manual reconfiguration. While the blast radius is limited to a single autoreply rule (not system-wide), the irreversible nature of deletion places it in the Destructive category.
From the tool's definition Tool name 'mail_autoreplies_delete' combined with description 'Delete an autoreply' explicitly performs an irreversible deletion operation on email autoreply configuration.
Attacks that exploit this kind of access
The rule that runs mail_autoreplies_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_autoreplies_delete, this is the rule to start with:
mail_autoreplies_delete 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, apply this rule, and every mail_autoreplies_delete call is checked against it from then on.
Questions about mail_autoreplies_delete
Delete an autoreply. 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.
Register the Hostinger MCP server in PolicyLayer and add a rule for mail_autoreplies_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.
mail_autoreplies_delete 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_autoreplies_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.
Set action: deny in the PolicyLayer policy for mail_autoreplies_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.
mail_autoreplies_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.
More on Hostinger, and thousands of servers like it.
Across the catalogue