check_email_setup
Diagnostic wizard for email tool configuration. Checks env vars (EMAIL_USER, EMAIL_PASS, etc.), optionally tests SMTP/IMAP connections, and returns step-by-step setup instructions for missing pieces. Supports Gmail, Outlook, Yahoo, and custom SMTP/IMAP. Run this FIRST before using send_email or r...
This record as markdown: /tools/io-github-homenshum-nodebench/check-email-setup.md
What check_email_setup does on Nodebench
AI agents call check_email_setup to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_email_setup is rated Low
This is primarily a diagnostic/read operation that retrieves and checks email configuration state. However, the medium severity reflects that it accesses and validates sensitive credentials (EMAIL_USER, EMAIL_PASS) and connection details, which could leak information if misused by an agent.
From the tool's definition 'Checks env vars', 'tests SMTP/IMAP connections', 'returns step-by-step setup instructions' — the tool reads and validates email configuration credentials and connection status without modifying them.
Attacks that exploit this kind of access
The rule that runs check_email_setup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_email_setup, this is the rule to start with:
check_email_setup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every check_email_setup call is checked against it from then on.
Questions about check_email_setup
Diagnostic wizard for email tool configuration. Checks env vars (EMAIL_USER, EMAIL_PASS, etc.), optionally tests SMTP/IMAP connections, and returns step-by-step setup instructions for missing pieces. Supports Gmail, Outlook, Yahoo, and custom SMTP/IMAP. Run this FIRST before using send_email or read_emails. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for check_email_setup: 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 Nodebench. Nothing to install.
check_email_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_email_setup 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 check_email_setup. 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.
check_email_setup is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue