mail_webhooks_test

Send a test event to a webhook.

SERVERHostinger SOURCEidugeni/hostinger-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/mail-webhooks-test.md

WHAT IT DOES

What mail_webhooks_test does on Hostinger

AI agents invoke mail_webhooks_test to trigger actions in Hostinger. 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.

RISK

Why mail_webhooks_test is rated High

This tool triggers an external HTTP request/operation by sending a test event to a configured webhook endpoint. It executes an outbound action whose effects depend on the webhook's configuration and recipient system. This is not a simple read, and while it's a 'test' action, it still fires an external operation with potential side effects on receiving systems.

From the tool's definition "Send a test event to a webhook"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mail_webhooks_test safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_webhooks_test, this is the rule to start with:

mail_webhooks_test Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_webhooks_test": {
      "limits": [
        {
          "counter": "mail_webhooks_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every mail_webhooks_test call is checked against it from then on.

FAQ

Questions about mail_webhooks_test

What does the mail_webhooks_test tool do? +

Send a test event to a webhook. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mail_webhooks_test? +

Register the Hostinger MCP server in PolicyLayer and add a rule for mail_webhooks_test: 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. Nothing to install.

What risk level is mail_webhooks_test? +

mail_webhooks_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mail_webhooks_test? +

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

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

mail_webhooks_test is provided by the Hostinger MCP server (idugeni/hostinger-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, and thousands of servers like it.

This server

All 284 Hostinger tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →