mail_listWebhooksV1
Retrieve a paginated list of webhooks belonging to the given mail order. Supports filtering by mailbox and status. The webhook secret is never included; it is returned only when a webhook is created or its secret is regenerated.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-listwebhooksv1.md
What mail_listWebhooksV1 does on Hostinger Api
AI agents call mail_listWebhooksV1 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 |
status | string | — | Filter webhooks by status |
orderId | string | Yes | Order resource ID |
per_page | integer | — | Number of items per page |
mailbox_id | string | — | Filter by the mailbox resource ID the webhooks are attached to |
Parameters from the server's own tool schema.
Why mail_listWebhooksV1 is rated Low
This tool retrieves and queries webhook data without modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects. The low severity reflects minimal risk from accidental or malicious use—listing webhooks alone cannot cause harm to systems or data.
From the tool's definition The tool name includes 'list' and the description explicitly states 'Retrieve a paginated list of webhooks'.
Attacks that exploit this kind of access
The rule that runs mail_listWebhooksV1 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_listWebhooksV1, this is the rule to start with:
mail_listWebhooksV1 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_listWebhooksV1 call is checked against it from then on.
Questions about mail_listWebhooksV1
Retrieve a paginated list of webhooks belonging to the given mail order. Supports filtering by mailbox and status. The webhook secret is never included; it is returned only when a webhook is created or its secret is regenerated. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
mail_listWebhooksV1 accepts 5 parameters: page, status, orderId, per_page, mailbox_id. 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_listWebhooksV1: 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_listWebhooksV1 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_listWebhooksV1 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_listWebhooksV1. 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_listWebhooksV1 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