test_external_account

Test IMAP+SMTP credentials without saving. Makes an outbound connection. Requires TREKMAIL_ALLOW_MIGRATION=true.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/test-external-account.md

WHAT IT DOES

What test_external_account does on TrekMail MCP Server

AI agents invoke test_external_account 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.

RISK

Why test_external_account is rated High

This tool actively initiates outbound network connections to external IMAP and SMTP servers to validate credentials. While it does not save data, it executes real network operations with external side effects. This falls under Execute rather than Read because it triggers external operations (outbound connections) rather than merely retrieving local data.

From the tool's definition 'Test IMAP+SMTP credentials without saving. Makes an outbound connection.'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_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 test_external_account, this is the rule to start with:

test_external_account Rate-limited

test_external_account 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_external_account": {
      "limits": [
        {
          "counter": "test_external_account_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every test_external_account call is checked against it from then on.

FAQ

Questions about test_external_account

What does the test_external_account tool do? +

Test IMAP+SMTP credentials without saving. Makes an outbound connection. Requires TREKMAIL_ALLOW_MIGRATION=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.

How do I enforce a policy on test_external_account? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for test_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 test_external_account? +

test_external_account is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_external_account? +

Yes. Add a rate_limit block to the test_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 test_external_account completely? +

Set action: deny in the PolicyLayer policy for test_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 test_external_account? +

test_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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →