New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

detect_external_account

Given an email address, return the provider preset (IMAP/SMTP host/port, app-password requirement) for connecting it.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about detect_external_account

What does the detect_external_account tool do? +

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.

How do I enforce a policy on detect_external_account? +

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.

What risk level is detect_external_account? +

detect_external_account is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit detect_external_account? +

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.

How do I block detect_external_account completely? +

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.

What MCP server provides detect_external_account? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TrekMail MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.