mail_updateWebhookV1

Partially update a webhook. Only the fields included in the request body are changed; omitted fields retain their current values. Pass "description": null to clear the description.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 61 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-updatewebhookv1.md

WHAT IT DOES

What mail_updateWebhookV1 does on Hostinger Api

AI agents use mail_updateWebhookV1 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	—	New URL to deliver events to
`name`	string	—	New human-readable name for the webhook
`events`	array	—	Replaces the full list of subscribed events
`status`	string	—	New status for the webhook
`webhookId`	string	Yes	Webhook ID (returned when the webhook was created)
`description`	string	—	New description, or null to clear it

Parameters from the server's own tool schema.

RISK

Why mail_updateWebhookV1 is rated Medium

This tool creates or modifies webhook configuration data reversibly. While webhooks can trigger external side effects when fired, this tool itself only updates webhook settings (description, presumably URL/event filters, etc.), not executing webhooks. The update is reversible — fields can be changed back or cleared.

From the tool's definition Tool name contains 'update' and description states 'Partially update a webhook' — modifies webhook configuration fields reversibly.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mail_updateWebhookV1 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_updateWebhookV1, this is the rule to start with:

mail_updateWebhookV1 Rate-limited

mail_updateWebhookV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_updateWebhookV1": {
      "limits": [
        {
          "counter": "mail_updatewebhookv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_updateWebhookV1 call is checked against it from then on.

FAQ

Questions about mail_updateWebhookV1

What does the mail_updateWebhookV1 tool do? +

Partially update a webhook. Only the fields included in the request body are changed; omitted fields retain their current values. Pass "description": null to clear the description. 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_updateWebhookV1 accept? +

mail_updateWebhookV1 accepts 6 parameters: url, name, events, status, webhookId, description. 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_updateWebhookV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for mail_updateWebhookV1: 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_updateWebhookV1? +

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

Can I rate-limit mail_updateWebhookV1? +

Yes. Add a rate_limit block to the mail_updateWebhookV1 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_updateWebhookV1 completely? +

Set action: deny in the PolicyLayer policy for mail_updateWebhookV1. 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_updateWebhookV1? +

mail_updateWebhookV1 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 382 Hostinger Api tools →

Across the catalogue

mail_create_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →