get_mail_client_setup
Get password-free IMAP and SMTP settings plus localized three-step guides for Gmail, Outlook, Apple Mail, Thunderbird, and other IMAP apps. For each shared mailbox with Read, reports durable native-access readiness, effective send_as_ready/send_as_reason, exact Inbox/Sent/Archive/Junk paths, read...
This record as markdown: /tools/trekmail-mcp-server/get-mail-client-setup.md
What get_mail_client_setup does on TrekMail MCP Server
AI agents call get_mail_client_setup 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_mail_client_setup is rated Low
Tool retrieves email configuration and capability metadata without modifying data or triggering actions.
From the tool's definition Get password-free IMAP and SMTP settings, reports durable native-access readiness, exact paths.
Attacks that exploit this kind of access
The rule that runs get_mail_client_setup 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_mail_client_setup, this is the rule to start with:
get_mail_client_setup 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_mail_client_setup call is checked against it from then on.
Questions about get_mail_client_setup
Get password-free IMAP and SMTP settings plus localized three-step guides for Gmail, Outlook, Apple Mail, Thunderbird, and other IMAP apps. For each shared mailbox with Read, reports durable native-access readiness, effective send_as_ready/send_as_reason, exact Inbox/Sent/Archive/Junk paths, read/flag/folder/move/delete/send-as capabilities, and whether SMTP saves a Sent copy. Wait for native_access_ready=true and, for sending, send_as_ready=true. delegated_send_addresses lists send-only team addresses as {id, email, display_name}, even when shared IMAP is disabled. Add them as extra From addresses in the mail app using the member’s own sign-in and app password. They have no shared folders; save sent mail in the member’s own Sent. The Message API cannot use these delegated addresses yet. The user always authenticates with the regular member mailbox address; no password or custom SMTP provider credential is returned. authentication.password_source says which password the mail app takes:. 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_mail_client_setup: 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_mail_client_setup 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_mail_client_setup 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_mail_client_setup. 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_mail_client_setup 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