mail_testWebhookV1
Send a test delivery to the webhook URL and return the result. Test requests are rate limited upstream.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-testwebhookv1.md
What mail_testWebhookV1 does on Hostinger Api
AI agents invoke mail_testWebhookV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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_testWebhookV1 is rated High
This tool triggers an external HTTP request to a webhook URL, which is an external operation with side effects (the webhook endpoint receives and may act on the test payload). It does not merely read data, nor does it irreversibly destroy or move money. The rate-limiting note confirms real requests are sent upstream, making this an Execute category action.
From the tool's definition "Send a test delivery to the webhook URL and return the result"
Attacks that exploit this kind of access
The rule that runs mail_testWebhookV1 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_testWebhookV1, this is the rule to start with:
mail_testWebhookV1 stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_testWebhookV1 call is checked against it from then on.
Questions about mail_testWebhookV1
Send a test delivery to the webhook URL and return the result. Test requests are rate limited upstream. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
mail_testWebhookV1 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_testWebhookV1: 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_testWebhookV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mail_testWebhookV1 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_testWebhookV1. 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_testWebhookV1 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.
Across the catalogue