enrich_by_email

Look up detailed person and company information using an email address. Returns verified business data including job title, company details, phone numbers, and social profiles.

Server LeadFuze-MCP-Server leadfuze/mcp-server
Category Read
Risk class Low
Parameters 00 required

What enrich_by_email does on LeadFuze-MCP-Server

AI agents call enrich_by_email to retrieve information from LeadFuze-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why enrich_by_email needs a policy

This tool queries a database to retrieve enriched contact and company information based on an email address. It has no side effects—it does not create, modify, delete, or execute operations. The worst-case misuse would be unauthorized data access or privacy violations, but the tool itself is read-only.

From the tool's definition Tool performs 'Look up' and 'Returns' operations on existing data. No modification, deletion, or execution of external operations described.

Questions about enrich_by_email

What does the enrich_by_email tool do? +

Look up detailed person and company information using an email address. Returns verified business data including job title, company details, phone numbers, and social profiles. It is categorised as a Read tool in the LeadFuze-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on enrich_by_email? +

Register the LeadFuze-MCP-Server MCP server in PolicyLayer and add a rule for enrich_by_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 LeadFuze-MCP-Server. Nothing to install.

What risk level is enrich_by_email? +

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

Can I rate-limit enrich_by_email? +

Yes. Add a rate_limit block to the enrich_by_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.

How do I block enrich_by_email completely? +

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

What MCP server provides enrich_by_email? +

enrich_by_email is provided by the LeadFuze-MCP-Server MCP server (leadfuze/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.