Open IMAP and SMTP, return per-account success and message counts. Use to validate credentials.
AI agents call account_test_connection to retrieve information from MCP Email Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a testing/validation utility that queries account status and retrieves connection information. It has no side effects on email data (no creation, modification, deletion, or execution of commands). The blast radius of misuse is minimal—an attacker could only gather account status information, not compromise email content or trigger destructive actions.
From the tool's definition Tool description states it opens IMAP and SMTP connections and returns 'success and message counts' for validation purposes.
Documented attack patterns abuse exactly the kind of access account_test_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Email Service, and nothing reaches the server without passing your rules. This is the rule we recommend for account_test_connection:
{
"version": "1",
"default": "deny",
"tools": {
"account_test_connection": {}
}
}account_test_connection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open IMAP and SMTP, return per-account success and message counts. Use to validate credentials. It is categorised as a Read tool in the MCP Email Service MCP Server, which means it retrieves data without modifying state.
Register the MCP Email Service MCP server in PolicyLayer and add a rule for account_test_connection: 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 MCP Email Service. Nothing to install.
account_test_connection 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 account_test_connection 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 account_test_connection. 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.
account_test_connection is provided by the MCP Email Service MCP server (leeguooooo/mailbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Email Service, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 MCP Email Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.