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.

SERVERHostinger Api SOURCEhostinger-api-mcp
Medium RISK CLASS
Category Write
Parameters 64 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about mail_createWebhookV1

What does the mail_createWebhookV1 tool do? +

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.

What parameters does mail_createWebhookV1 accept? +

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.

How do I enforce a policy on mail_createWebhookV1? +

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.

What risk level is mail_createWebhookV1? +

mail_createWebhookV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mail_createWebhookV1? +

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.

How do I block mail_createWebhookV1 completely? +

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.

What MCP server provides mail_createWebhookV1? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.