mail_createWebhookV1
Create a webhook for the given mailbox. The generated secret is returned only in this response and is sent as a bearer token with every delivery.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-createwebhookv1.md
What mail_createWebhookV1 does on Hostinger Api
AI agents use mail_createWebhookV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Publicly reachable URL that receives the webhook POST requests |
name | string | Yes | Human-readable name for this webhook |
events | array | Yes | Events that trigger this webhook |
status | string | — | Initial status of the webhook |
mailboxId | string | Yes | Mailbox resource ID |
description | string | — | Optional description of the webhook's purpose |
Parameters from the server's own tool schema.
Why mail_createWebhookV1 is rated Medium
An AI agent can call mail_createWebhookV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs mail_createWebhookV1 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_createWebhookV1, this is the rule to start with:
mail_createWebhookV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_createWebhookV1 call is checked against it from then on.
Questions about mail_createWebhookV1
Create a webhook for the given mailbox. The generated secret is returned only in this response and is sent as a bearer token with every delivery. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mail_createWebhookV1 accepts 6 parameters: url, name, events, status, mailboxId, description. Required: url, name, events, mailboxId. 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_createWebhookV1: 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_createWebhookV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mail_createWebhookV1 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_createWebhookV1. 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_createWebhookV1 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