update_smtp_config
Update the SMTP configuration. Switch between platform and custom SMTP, or update custom SMTP settings. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.
This record as markdown: /tools/trekmail-mcp-server/update-smtp-config.md
What update_smtp_config does on TrekMail MCP Server
AI agents invoke update_smtp_config to trigger actions in TrekMail MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why update_smtp_config is rated High
This tool modifies core email infrastructure configuration (SMTP routing). While technically a Write operation, changing SMTP settings can redirect all outgoing email to an attacker-controlled server, cause mail delivery failures, or expose credentials — effects that are operationally severe and partially irreversible in impact.
From the tool's definition 'Update the SMTP configuration. Switch between platform and custom SMTP, or update custom SMTP settings. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.'
Attacks that exploit this kind of access
The rule that runs update_smtp_config 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 update_smtp_config, this is the rule to start with:
update_smtp_config stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 update_smtp_config call is checked against it from then on.
Questions about update_smtp_config
Update the SMTP configuration. Switch between platform and custom SMTP, or update custom SMTP settings. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. It is categorised as a Execute tool in the TrekMail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for update_smtp_config: 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.
update_smtp_config is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the update_smtp_config 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 update_smtp_config. 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.
update_smtp_config 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.
Across the catalogue