get_smtp_test_status

Poll the result of an SMTP connection test by job_id.

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/get-smtp-test-status.md

WHAT IT DOES

What get_smtp_test_status does on TrekMail MCP Server

AI agents call get_smtp_test_status 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.

RISK

Why get_smtp_test_status is rated Low

The tool polls and retrieves the status of a previously initiated SMTP test. It performs no modifications, deletions, or external operations—it only queries and returns data about an existing test job. This is a classic Read operation with minimal risk.

From the tool's definition Tool name 'get_smtp_test_status' and description 'Poll the result of an SMTP connection test by job_id' indicate a read-only query operation that retrieves status information.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_smtp_test_status Allowed

get_smtp_test_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_smtp_test_status": {}
  }
}

ALLOW ONLY 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 get_smtp_test_status call is checked against it from then on.

FAQ

Questions about get_smtp_test_status

What does the get_smtp_test_status tool do? +

Poll the result of an SMTP connection test by job_id. 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 get_smtp_test_status? +

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

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

Can I rate-limit get_smtp_test_status? +

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

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

get_smtp_test_status 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 →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →