Find personal email addresses from B2B profile URLs. Useful for reaching contacts through their personal channels when professional emails are not available.
AI agents call find_personal_email to retrieve information from LeadMagic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation: it retrieves and queries personal email data from B2B profiles without creating, modifying, deleting, or executing any actions. Severity is medium because while the tool itself performs a benign retrieval, the output (personal email addresses) could be misused for unsolicited contact, spam, or social engineering campaigns if an AI agent acted on this data without proper consent — creating…
From the tool's definition Tool description states it 'Find[s] personal email addresses from B2B profile URLs' — a retrieval operation with no modification or deletion of data. The tool queries existing profile information and returns email addresses without side effects.
Documented attack patterns abuse exactly the kind of access find_personal_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LeadMagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_personal_email:
{
"version": "1",
"default": "deny",
"tools": {
"find_personal_email": {}
}
}find_personal_email 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.
Find personal email addresses from B2B profile URLs. Useful for reaching contacts through their personal channels when professional emails are not available. It is categorised as a Read tool in the LeadMagic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LeadMagic MCP Server MCP server in PolicyLayer and add a rule for find_personal_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 LeadMagic MCP Server. Nothing to install.
find_personal_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 find_personal_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 find_personal_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.
find_personal_email is provided by the LeadMagic MCP Server MCP server (leadmagic/leadmagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LeadMagic 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.
19 LeadMagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.