mail_listAPITokensV1
Retrieve a paginated list of [Hostinger Email API](https://api.mail.hostinger.com/) tokens across all your mail orders, optionally filtered by order. Plaintext tokens are never included; they are returned only when a token is created.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-listapitokensv1.md
What mail_listAPITokensV1 does on Hostinger Api
AI agents call mail_listAPITokensV1 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 |
order_id | string | — | Filter tokens by order resource ID. Single value or comma-separated list. |
per_page | integer | — | Number of items per page |
Parameters from the server's own tool schema.
Why mail_listAPITokensV1 is rated Low
This tool retrieves existing API tokens without modifying, executing, deleting, or creating them. It is a read-only query operation. Severity is medium rather than low because exposure of token metadata (even without plaintext values) to an unrestricted AI agent could facilitate further reconnaissance and targeted attacks on email infrastructure, though the actual token values themselves are protected from retrieval.
From the tool's definition Tool name contains 'list' and description states 'Retrieve a paginated list of...tokens'. The description explicitly clarifies that 'Plaintext tokens are never included; they are returned only when a token is created', confirming this is purely a retrieval…
Attacks that exploit this kind of access
The rule that runs mail_listAPITokensV1 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_listAPITokensV1, this is the rule to start with:
mail_listAPITokensV1 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_listAPITokensV1 call is checked against it from then on.
Questions about mail_listAPITokensV1
Retrieve a paginated list of [Hostinger Email API](https://api.mail.hostinger.com/) tokens across all your mail orders, optionally filtered by order. Plaintext tokens are never included; they are returned only when a token is created. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
mail_listAPITokensV1 accepts 3 parameters: page, order_id, per_page. 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_listAPITokensV1: 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_listAPITokensV1 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_listAPITokensV1 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_listAPITokensV1. 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_listAPITokensV1 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