get_auto_reply
Get the vacation auto-reply settings for a mailbox. Shows whether auto-reply is enabled, the subject, message body, and date range.
This record as markdown: /tools/trekmail-mcp-server/get-auto-reply.md
What get_auto_reply does on TrekMail MCP Server
AI agents call get_auto_reply to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_auto_reply is rated Low
This tool retrieves configuration data about auto-reply settings for a mailbox. It performs a read-only query of existing settings without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could learn auto-reply configurations but cannot alter email infrastructure or cause harm through this tool alone.
From the tool's definition Tool name is 'get_auto_reply' with description stating it 'Get[s] the vacation auto-reply settings' and 'Shows whether auto-reply is enabled, the subject, message body, and date range.' The verb 'Get' and 'Shows' indicate a retrieval operation with no…
Attacks that exploit this kind of access
The rule that runs get_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 get_auto_reply, this is the rule to start with:
get_auto_reply 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 TrekMail MCP Server, apply this rule, and every get_auto_reply call is checked against it from then on.
Questions about get_auto_reply
Get the vacation auto-reply settings for a mailbox. Shows whether auto-reply is enabled, the subject, message body, and date range. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_auto_reply 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 get_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 get_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.
get_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