test_smtp_connection · BasicSec MCP Server MCP

WHAT IT DOES

What test_smtp_connection does on BasicSec MCP Server

AI agents invoke test_smtp_connection to trigger actions in BasicSec 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 IT NEEDS A POLICY

Why test_smtp_connection needs a policy

This tool actively opens a TCP connection to a remote SMTP host and probes for STARTTLS support, which constitutes executing an external operation (network probe). It is not a passive read of existing data; it triggers real outbound connections whose effects depend on the target hostname argument. Severity is medium because misuse could be used to probe unauthorized hosts or generate unwanted traffic.

From the tool's definition 'Test SMTP connection and STARTTLS support' — actively initiates a network connection to an external SMTP server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_smtp_connection Rate-limited

test_smtp_connection 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_smtp_connection": {
      "limits": [
        {
          "counter": "test_smtp_connection_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BasicSec MCP Server, so you can run agents against it safely.

FAQ

Questions about test_smtp_connection

What does the test_smtp_connection tool do? +

Test SMTP connection and STARTTLS support for a specific hostname. It is categorised as a Execute tool in the BasicSec 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_connection? +

Register the BasicSec MCP Server MCP server in PolicyLayer and add a rule for test_smtp_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 BasicSec MCP Server. Nothing to install.

What risk level is test_smtp_connection? +

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

Can I rate-limit test_smtp_connection? +

Yes. Add a rate_limit block to the test_smtp_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.

How do I block test_smtp_connection completely? +

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

What MCP server provides test_smtp_connection? +

test_smtp_connection is provided by the BasicSec MCP Server MCP server (marlinkcyber/basicsec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.