This record as markdown: /tools/hostinger-mcp/mail-mailboxes-create.md
What mail_mailboxes_create does on Hostinger
AI agents use mail_mailboxes_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_mailboxes_create is rated Medium
Creating a mailbox is a reversible write operation that adds a new email resource to the account. It modifies account state but does not delete data or trigger irreversible changes, placing it in the Write category.
From the tool's definition Tool name 'mail_mailboxes_create' and description 'Create a new mailbox' indicate a create operation that modifies email account configuration by adding a new mailbox resource.
Attacks that exploit this kind of access
The rule that runs mail_mailboxes_create 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_mailboxes_create, this is the rule to start with:
mail_mailboxes_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_mailboxes_create call is checked against it from then on.
Questions about mail_mailboxes_create
Create a new mailbox. 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.
Register the Hostinger MCP server in PolicyLayer and add a rule for mail_mailboxes_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.
mail_mailboxes_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mail_mailboxes_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.
Set action: deny in the PolicyLayer policy for mail_mailboxes_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.
mail_mailboxes_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.
This server
Across the catalogue