New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mail_aliases_create

Create an email alias.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What mail_aliases_create does on Hostinger

AI agents use mail_aliases_create to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.

Why mail_aliases_create is rated Medium

This tool creates an email alias, which is a reversible modification to email infrastructure. It does not delete data (Destructive), move money (Financial), or execute arbitrary code (Execute). While email configuration changes can have operational impact if misconfigured, the action is fundamentally a create/write operation.

From the tool's definition Tool name 'mail_aliases_create' and description 'Create an email alias' indicate creation of a new resource that modifies email configuration.

Questions about mail_aliases_create

What does the mail_aliases_create tool do? +

Create an email alias. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mail_aliases_create? +

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

mail_aliases_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mail_aliases_create? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.