Verify if an email address is valid and deliverable via DNS MX + SMTP handshake. Returns confidence score (0-100).
AI agents call verify_email to retrieve information from Prospector MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves deliverability status through legitimate DNS and SMTP protocol checks (standard email validation). It has no side effects on data or systems beyond querying mail server responsiveness. While email verification could potentially support phishing or spam campaigns, the tool itself is a passive read operation that simply tests whether an email address is reachable.
From the tool's definition Tool performs DNS MX + SMTP handshake verification with no data modification. Returns a confidence score without creating, modifying, deleting, or executing arbitrary actions. The description states 'Verify if an email address is valid' — a query operation.
Attacks that exploit this kind of access
Verify if an email address is valid and deliverable via DNS MX + SMTP handshake. Returns confidence score (0-100). It is categorised as a Read tool in the Prospector MCP MCP Server, which means it retrieves data without modifying state.
Register the Prospector MCP server in PolicyLayer and add a rule for verify_email: 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 Prospector MCP. Nothing to install.
verify_email 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 verify_email 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 verify_email. 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.
verify_email is provided by the Prospector MCP server (josiebot26/prospector-mcp-email-finder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →