detect_external_account
Given an email address, return the provider preset (IMAP/SMTP host/port, app-password requirement) for connecting it.
This record as markdown: /tools/trekmail-mcp-server/detect-external-account.md
What detect_external_account does on TrekMail MCP Server
AI agents call detect_external_account 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 detect_external_account is rated Low
This tool queries and retrieves configuration metadata about email providers based on an email address input. It has no side effects—it does not create, modify, delete data, execute code, or trigger external operations. It is purely informational lookup, fitting the 'Read' category.
From the tool's definition Tool 'detect_external_account' returns provider preset information (IMAP/SMTP host/port, app-password requirement) for a given email address.
Attacks that exploit this kind of access
The rule that runs detect_external_account 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 detect_external_account, this is the rule to start with:
detect_external_account 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 detect_external_account call is checked against it from then on.
Questions about detect_external_account
Given an email address, return the provider preset (IMAP/SMTP host/port, app-password requirement) for connecting it. 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 detect_external_account: 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.
detect_external_account 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 detect_external_account 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 detect_external_account. 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.
detect_external_account 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