mail_createForwarderV1
Create a forwarder from the given mailbox to the destination address. The destination receives a confirmation email and forwarding becomes active only after it is confirmed.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-createforwarderv1.md
What mail_createForwarderV1 does on Hostinger Api
AI agents use mail_createForwarderV1 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 |
|---|---|---|---|
mailboxId | string | Yes | Mailbox resource ID |
destination | string | Yes | Email address the messages will be forwarded to |
is_keep_copy_enabled | boolean | — | Whether to keep a copy of forwarded messages in the mailbox. Defaults to false. |
Parameters from the server's own tool schema.
Why mail_createForwarderV1 is rated Medium
This tool creates a new email forwarding configuration, which modifies email routing settings. This is a Write operation (creates data/configuration reversibly). Severity is medium because misconfigured forwarders could redirect sensitive emails or disrupt communication, but the impact is limited to email routing and can be undone.
From the tool's definition Tool name is 'mail_createForwarderV1' and description states 'Create a forwarder' — this creates/adds a new email forwarding rule. The operation is reversible (forwarders can be deleted, as evidenced by sibling delete operations on this server).
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs mail_createForwarderV1 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_createForwarderV1, this is the rule to start with:
mail_createForwarderV1 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_createForwarderV1 call is checked against it from then on.
Questions about mail_createForwarderV1
Create a forwarder from the given mailbox to the destination address. The destination receives a confirmation email and forwarding becomes active only after it is confirmed. 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_createForwarderV1 accepts 3 parameters: mailboxId, destination, is_keep_copy_enabled. Required: mailboxId, destination. 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_createForwarderV1: 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_createForwarderV1 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_createForwarderV1 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_createForwarderV1. 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_createForwarderV1 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