mail_listForwardersV1
Retrieve a paginated list of forwarders across all mailboxes of a mail order.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-listforwardersv1.md
What mail_listForwardersV1 does on Hostinger Api
AI agents call mail_listForwardersV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number |
orderId | string | Yes | Order resource ID |
per_page | integer | — | Number of items per page |
Parameters from the server's own tool schema.
Why mail_listForwardersV1 is rated Low
This tool retrieves and lists existing email forwarder data. It performs a read-only operation that queries information from the mail order without creating, modifying, deleting, or executing any actions. The data returned may include configuration details, but the tool itself has no side effects beyond returning information.
From the tool's definition Tool name 'mail_listForwardersV1' and description 'Retrieve a paginated list of forwarders across all mailboxes' indicate a query/retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs mail_listForwardersV1 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_listForwardersV1, this is the rule to start with:
mail_listForwardersV1 is read-only, so it stays allowed. 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_listForwardersV1 call is checked against it from then on.
Questions about mail_listForwardersV1
Retrieve a paginated list of forwarders across all mailboxes of a mail order. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
mail_listForwardersV1 accepts 3 parameters: page, orderId, per_page. Required: orderId. 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_listForwardersV1: 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_listForwardersV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mail_listForwardersV1 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_listForwardersV1. 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_listForwardersV1 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