This record as markdown: /tools/hostinger-mcp/mail-webhooks-get.md
What mail_webhooks_get does on Hostinger
AI agents call mail_webhooks_get to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mail_webhooks_get is rated Low
This tool retrieves or queries webhook configuration details for mail services. It performs a read-only operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker could only gain visibility into existing webhook configurations, not alter them or cause operational damage.
From the tool's definition Tool name 'mail_webhooks_get' and description 'Get webhook details' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs mail_webhooks_get 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_get, this is the rule to start with:
mail_webhooks_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every mail_webhooks_get call is checked against it from then on.
Questions about mail_webhooks_get
Get webhook details. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for mail_webhooks_get: 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.
mail_webhooks_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mail_webhooks_get 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_webhooks_get. 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_webhooks_get 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.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue