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

test_smtp

Test an SMTP connection with the provided credentials. Returns a job_id to poll for results.

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-smtp.md

What test_smtp does on TrekMail MCP Server

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

Why test_smtp is rated High

This tool executes an outbound SMTP connection test against an external server, which is an active network operation with side effects (connection attempts, authentication handshakes). It doesn't merely read data locally; it triggers an external operation. Severity is medium because misuse could leak credentials or be used to probe/enumerate SMTP servers, but it doesn't directly modify or destroy data.

From the tool's definition 'Test an SMTP connection with the provided credentials' — actively initiates a network connection to an external SMTP server using supplied credentials

Questions about test_smtp

What does the test_smtp tool do? +

Test an SMTP connection with the provided credentials. Returns a job_id to poll for results. 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_smtp? +

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

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

Can I rate-limit test_smtp? +

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

Set action: deny in the PolicyLayer policy for test_smtp. 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_smtp? +

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