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.

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-getwebhookv1.md

WHAT IT DOES

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.

RISK

Why mail_getWebhookV1 is rated Low

Even though mail_getWebhookV1 only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

mail_getWebhookV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_getWebhookV1": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about mail_getWebhookV1

What does the mail_getWebhookV1 tool do? +

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.

What parameters does mail_getWebhookV1 accept? +

mail_getWebhookV1 accepts 1 parameter: webhookId. Required: webhookId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mail_getWebhookV1? +

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.

What risk level is mail_getWebhookV1? +

mail_getWebhookV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mail_getWebhookV1? +

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.

How do I block mail_getWebhookV1 completely? +

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.

What MCP server provides mail_getWebhookV1? +

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.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →