Send data to a Clay webhook to trigger a table-based enrichment workflow. Clay tables run custom enrichment sequences (waterfall emails, phone lookups, intent signals, etc.). The webhook URL is unique to each Clay table — get it from your Clay table settings. Args: - webhook_url (string): The Cla...
AI agents invoke clay_trigger_enrichment to trigger actions in Sales Intelligence. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While the tool itself is a webhook trigger (which could be classified as Write), the key distinguishing factor is that it initiates a 'custom enrichment sequence' with externally visible side effects including potential email sends and phone lookups. This goes beyond simple data creation—it triggers automated external actions that depend on the data provided and the specific Clay table configuration.
From the tool's definition Tool description states it 'Send data to a Clay webhook to trigger a table-based enrichment workflow' and mentions that 'Clay tables run custom enrichment sequences (waterfall emails, phone lookups, intent signals, etc.)'.
Attacks that exploit this kind of access
Send data to a Clay webhook to trigger a table-based enrichment workflow. Clay tables run custom enrichment sequences (waterfall emails, phone lookups, intent signals, etc.). The webhook URL is unique to each Clay table — get it from your Clay table settings. Args: - webhook_url (string): The Clay webhook URL for the enrichment table - data (object): Key-value pairs to send (e.g. {. It is categorised as a Execute tool in the Sales Intelligence MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sales Intelligence MCP server in PolicyLayer and add a rule for clay_trigger_enrichment: 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_trigger_enrichment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clay_trigger_enrichment 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_trigger_enrichment. 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_trigger_enrichment 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 →