Check email security configuration
AI agents call check_email_security to retrieve information from External Reconnaissance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes email security configuration data without side effects. While reconnaissance can inform attacks, the tool itself is purely informational and does not execute code, modify systems, or trigger external operations. It aligns with the Read category as a query/fetch operation against a target domain's email infrastructure configuration.
From the tool's definition Tool performs 'Check email security configuration' which is reconnaissance-focused. The server description identifies this as part of 'email security analysis' activities.
Documented attack patterns abuse exactly the kind of access check_email_security gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and External Reconnaissance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_email_security:
{
"version": "1",
"default": "deny",
"tools": {
"check_email_security": {}
}
}check_email_security is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check email security configuration. It is categorised as a Read tool in the External Reconnaissance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the External Reconnaissance MCP Server MCP server in PolicyLayer and add a rule for check_email_security: 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 External Reconnaissance MCP Server. Nothing to install.
check_email_security 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_security 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_security. 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_security is provided by the External Reconnaissance MCP Server MCP server (naebo/mcp-external-recon-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from External Reconnaissance MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 External Reconnaissance MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.