mail_updateAutoreplyV1

Replace the autoreply with the given content and schedule. Omitted optional fields are cleared: omit starts_at to activate the autoreply immediately and omit ends_at to keep it active indefinitely.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 63 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-updateautoreplyv1.md

WHAT IT DOES

What mail_updateAutoreplyV1 does on Hostinger Api

AI agents use mail_updateAutoreplyV1 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
`starts_at`	string	—	When the autoreply becomes active. Defaults to now.
`autoreplyId`	string	Yes	Autoreply resource ID
`display_name`	string	—	Sender display name used for the reply

Parameters from the server's own tool schema.

RISK

Why mail_updateAutoreplyV1 is rated Medium

This is a Write operation because it creates or modifies data reversibly (updating autoreply content and scheduling). It does not delete data irreversibly, execute arbitrary code, or involve financial transactions. The severity is medium because misconfiguration could disrupt email communications for a mailbox user, but the change is reversible and limited in blast radius to autoreply functionality only.

From the tool's definition Tool performs 'Replace the autoreply with the given content and schedule' — this modifies email autoreply settings. The description indicates the tool updates/overwrites autoreply configuration, which is a reversible modification operation.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mail_updateAutoreplyV1 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_updateAutoreplyV1, this is the rule to start with:

mail_updateAutoreplyV1 Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_updateAutoreplyV1": {
      "limits": [
        {
          "counter": "mail_updateautoreplyv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mail_updateAutoreplyV1

What does the mail_updateAutoreplyV1 tool do? +

Replace the autoreply with the given content and schedule. Omitted optional fields are cleared: 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.

What parameters does mail_updateAutoreplyV1 accept? +

mail_updateAutoreplyV1 accepts 6 parameters: body, ends_at, subject, starts_at, autoreplyId, display_name. Required: body, subject, autoreplyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mail_updateAutoreplyV1? +

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

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

Can I rate-limit mail_updateAutoreplyV1? +

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

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

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

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 382 Hostinger Api tools →

Across the catalogue

mail_create_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →