mail_getWebhookV1
Retrieve the details of a single webhook. 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-getwebhookv1.md
What mail_getWebhookV1 does on Hostinger Api
AI agents call mail_getWebhookV1 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 |
|---|---|---|---|
webhookId | string | Yes | Webhook ID (returned when the webhook was created) |
Parameters from the server's own tool schema.
Why mail_getWebhookV1 is rated Low
This tool retrieves webhook metadata without modifying, creating, or deleting any data. The explicit note that secrets are not included in retrieval further confirms it is purely informational. The blast radius of an AI agent misusing this to enumerate webhooks is minimal—no data destruction or financial impact.
From the tool's definition Tool name contains 'get' and description states 'Retrieve the details of a single webhook' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs mail_getWebhookV1 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_getWebhookV1, this is the rule to start with:
mail_getWebhookV1 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_getWebhookV1 call is checked against it from then on.
Questions about mail_getWebhookV1
Retrieve the details of a single webhook. 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_getWebhookV1 accepts 1 parameter: webhookId. Required: webhookId. 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_getWebhookV1: 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_getWebhookV1 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_getWebhookV1 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_getWebhookV1. 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_getWebhookV1 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