New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mail_createCatchAllV1

Create a catch-all that routes all messages sent to unknown addresses of the domain to the given mailbox. The mailbox address receives a confirmation email and the catch-all becomes active only after it is confirmed. A domain can have only one catch-all.

SERVERHostinger Api SOURCEhostinger-api-mcp
Medium RISK CLASS
Category Write
Parameters 11 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-createcatchallv1.md

What mail_createCatchAllV1 does on Hostinger Api

AI agents use mail_createCatchAllV1 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
mailboxId string Yes Mailbox resource ID

Parameters from the server's own tool schema.

Why mail_createCatchAllV1 is rated Medium

This tool creates a new catch-all email rule that modifies email routing behavior on a domain. It is a Write operation because it creates a new configuration that is reversible (catch-alls can be deleted/modified).

From the tool's definition Tool name 'mail_createCatchAllV1' with description 'Create a catch-all' indicates it creates a new email routing configuration.

Risk signalsBulk/mass operation — affects multiple targets

Questions about mail_createCatchAllV1

What does the mail_createCatchAllV1 tool do? +

Create a catch-all that routes all messages sent to unknown addresses of the domain to the given mailbox. The mailbox address receives a confirmation email and the catch-all becomes active only after it is confirmed. A domain can have only one catch-all. 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_createCatchAllV1 accept? +

mail_createCatchAllV1 accepts 1 parameter: mailboxId. Required: mailboxId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mail_createCatchAllV1? +

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

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

Can I rate-limit mail_createCatchAllV1? +

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

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

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