imap_check

Check IMAP server connectivity. Reads server greeting and capabilities. Tests STARTTLS for port 143; uses implicit TLS for port 993. Does not authenticate.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/imap-check.md

WHAT IT DOES

What imap_check does on Mcp Nettools

AI agents call imap_check to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why imap_check is rated Low

This tool performs a read-only diagnostic check against IMAP servers. It establishes a connection and retrieves server metadata (greeting, capabilities, TLS support) but does not send commands, modify data, or trigger actions. The absence of authentication and emphasis on passive inspection confirms this is a Read operation. Severity is low as misuse would only expose IMAP server configuration details.

From the tool's definition Tool description states it 'Reads server greeting and capabilities' and 'Does not authenticate.' The operations are passive checks that retrieve information without modifying, executing code, or triggering external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs imap_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For imap_check, this is the rule to start with:

imap_check Allowed

imap_check 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": {
    "imap_check": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every imap_check call is checked against it from then on.

FAQ

Questions about imap_check

What does the imap_check tool do? +

Check IMAP server connectivity. Reads server greeting and capabilities. Tests STARTTLS for port 143; uses implicit TLS for port 993. Does not authenticate. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on imap_check? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for imap_check: 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 Nettools. Nothing to install.

What risk level is imap_check? +

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

Can I rate-limit imap_check? +

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

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

imap_check is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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