Test a domain
AI agents invoke test_domain_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.
The tool name indicates it performs an SMTP test against a domain, which involves executing an external network operation (connecting to a remote SMTP server). This is not a passive read but an active probe that triggers real network connections. The description is minimal ('Test a domain'), so confidence is moderate, but the SMTP context strongly implies execution of an external operation.
From the tool's definition 'Test a domain' and 'test_domain_smtp' — triggers an active SMTP connection/probe against a domain's mail server
Attacks that exploit this kind of access
Test a domain. 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.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for test_domain_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.
test_domain_smtp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_domain_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.
Set action: deny in the PolicyLayer policy for test_domain_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.
test_domain_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →