mail_createMailboxV1
Create a mailbox under the given mail order. The full email address is composed from the given local part and the domain of the order.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-createmailboxv1.md
What mail_createMailboxV1 does on Hostinger Api
AI agents use mail_createMailboxV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
orderId | string | Yes | Order resource ID |
password | string | Yes | Mailbox password. Minimum 8 characters with uppercase, lowercase, number and special character. |
local_part | string | Yes | Local part of the mailbox address (the part before the @). The domain is taken from the order. Must start and end with a letter or digit; single dots, underscor |
Parameters from the server's own tool schema.
Why mail_createMailboxV1 is rated Medium
An AI agent can call mail_createMailboxV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs mail_createMailboxV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_createMailboxV1, this is the rule to start with:
mail_createMailboxV1 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 Api, apply this rule, and every mail_createMailboxV1 call is checked against it from then on.
Questions about mail_createMailboxV1
Create a mailbox under the given mail order. The full email address is composed from the given local part and the domain of the order. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mail_createMailboxV1 accepts 3 parameters: orderId, password, local_part. Required: orderId, password, local_part. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for mail_createMailboxV1: 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 Api. Nothing to install.
mail_createMailboxV1 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_createMailboxV1 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_createMailboxV1. 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_createMailboxV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue