mail_changeMailboxPasswordV1
Change the password of a mailbox.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-changemailboxpasswordv1.md
What mail_changeMailboxPasswordV1 does on Hostinger Api
AI agents use mail_changeMailboxPasswordV1 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 |
|---|---|---|---|
password | string | Yes | New mailbox password. Minimum 8 characters with uppercase, lowercase, number and special character; must not be a commonly used password. |
mailboxId | string | Yes | Mailbox resource ID |
Parameters from the server's own tool schema.
Why mail_changeMailboxPasswordV1 is rated Medium
This tool modifies the password of a mailbox, which is a write operation that changes credentials. It's reversible (password can be changed again), but misuse could lock out legitimate users from their email, making it high severity.
From the tool's definition Change the password of a mailbox
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs mail_changeMailboxPasswordV1 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_changeMailboxPasswordV1, this is the rule to start with:
mail_changeMailboxPasswordV1 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_changeMailboxPasswordV1 call is checked against it from then on.
Questions about mail_changeMailboxPasswordV1
Change the password of a mailbox. 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_changeMailboxPasswordV1 accepts 2 parameters: password, mailboxId. Required: password, mailboxId. 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_changeMailboxPasswordV1: 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_changeMailboxPasswordV1 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_changeMailboxPasswordV1 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_changeMailboxPasswordV1. 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_changeMailboxPasswordV1 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