Enrich a person
AI agents call clay_enrich_person to retrieve information from Sales Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs data enrichment via Clay, which is a standard lead enrichment platform. Enrichment operations retrieve additional contact and firmographic data about prospects—this is fundamentally a Read operation that gathers intelligence without creating, modifying, deleting, or executing code.
From the tool's definition Tool name is 'clay_enrich_person' with description 'Enrich a person'. 'Enrich' in the context of data enrichment platforms like Clay means to retrieve and append additional data attributes about a person (e.g., email, phone, company details) from external…
Attacks that exploit this kind of access
Enrich a person. It is categorised as a Read tool in the Sales Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Sales Intelligence MCP server in PolicyLayer and add a rule for clay_enrich_person: 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 Sales Intelligence. Nothing to install.
clay_enrich_person 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 clay_enrich_person 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 clay_enrich_person. 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.
clay_enrich_person is provided by the Sales Intelligence MCP server (jbalbu01/sales-intelligence-mcp-server). 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 →