set_auto_reply
Configure the vacation auto-reply for a mailbox. Set a custom subject, message body, optional date range, and whether to skip mailing lists. Each sender receives the reply at most once every 7 days. Starter, Pro, and Agency plans.
This record as markdown: /tools/trekmail-mcp-server/set-auto-reply.md
What set_auto_reply does on TrekMail MCP Server
AI agents use set_auto_reply to create or update resources in TrekMail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.
Why set_auto_reply is rated Medium
This tool modifies mailbox auto-reply configuration (subject, body, date range, mailing list filtering), which is reversible and represents a Write action. It lacks the destructive nature of deletion, the irreversibility of destructive operations, or the external execution hazards of Execute tools.
From the tool's definition Tool configures and sets auto-reply settings for a mailbox with custom subject and message body, which modifies mailbox configuration reversibly. Description uses 'Configure' and 'Set' indicating data modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_auto_reply safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_auto_reply, this is the rule to start with:
set_auto_reply 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 TrekMail MCP Server, apply this rule, and every set_auto_reply call is checked against it from then on.
Questions about set_auto_reply
Configure the vacation auto-reply for a mailbox. Set a custom subject, message body, optional date range, and whether to skip mailing lists. Each sender receives the reply at most once every 7 days. Starter, Pro, and Agency plans. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for set_auto_reply: 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 TrekMail MCP Server. Nothing to install.
set_auto_reply 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 set_auto_reply 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 set_auto_reply. 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.
set_auto_reply is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue