get_smtp_config
Get the current SMTP configuration for the account, including mode (platform/custom) and connection details.
This record as markdown: /tools/trekmail-mcp-server/get-smtp-config.md
What get_smtp_config does on TrekMail MCP Server
AI agents call get_smtp_config 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_smtp_config is rated Low
This tool retrieves SMTP configuration data without modifying it, placing it in the Read category. However, the sensitivity is elevated to 'medium' severity because the returned connection details are security-critical infrastructure information.
From the tool's definition Tool name and description: 'Get the current SMTP configuration for the account, including mode (platform/custom) and connection details.' The verb 'get' and 'retrieve' pattern indicates data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs get_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 get_smtp_config, this is the rule to start with:
get_smtp_config 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_smtp_config call is checked against it from then on.
Questions about get_smtp_config
Get the current SMTP configuration for the account, including mode (platform/custom) and connection details. 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_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.
get_smtp_config 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_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 get_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.
get_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.
This server
Across the catalogue