mail_createAutoreplyV1
Create an automatic reply for the given mailbox. A mailbox can have only one autoreply. Omit starts_at to activate the autoreply immediately and omit ends_at to keep it active indefinitely.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-createautoreplyv1.md
What mail_createAutoreplyV1 does on Hostinger Api
AI agents use mail_createAutoreplyV1 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 |
|---|---|---|---|
body | string | Yes | Body of the automatic reply |
ends_at | string | — | When the autoreply stops. Omit for an indefinite autoreply. |
subject | string | Yes | Subject of the automatic reply |
mailboxId | string | Yes | Mailbox resource ID |
starts_at | string | — | When the autoreply becomes active. Defaults to now. |
display_name | string | — | Sender display name used for the reply |
Parameters from the server's own tool schema.
Why mail_createAutoreplyV1 is rated Medium
This tool creates or modifies mailbox settings (autoreply configuration) reversibly. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), nor move money (would be Financial). The severity is medium because misuse could disrupt email communications or enable spam/impersonation, but the changes are reversible by deleting or modifying the autoreply.
From the tool's definition Tool name contains 'create' and description states 'Create an automatic reply for the given mailbox', indicating data creation/modification. The tool modifies email configuration by setting up autoreply rules.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs mail_createAutoreplyV1 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_createAutoreplyV1, this is the rule to start with:
mail_createAutoreplyV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every mail_createAutoreplyV1 call is checked against it from then on.
Questions about mail_createAutoreplyV1
Create an automatic reply for the given mailbox. A mailbox can have only one autoreply. Omit starts_at to activate the autoreply immediately and omit ends_at to keep it active indefinitely. 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.
mail_createAutoreplyV1 accepts 6 parameters: body, ends_at, subject, mailboxId, starts_at, display_name. Required: body, subject, mailboxId. 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_createAutoreplyV1: 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_createAutoreplyV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mail_createAutoreplyV1 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_createAutoreplyV1. 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_createAutoreplyV1 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.
This server
Across the catalogue