POST /v1/contact/enrich. Enrich specific contacts by LinkedIn URL or name+domain. Returns a job_id (async, 202).
AI agents use contact_enrich to create or update resources in DataMerge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DataMerge MCP environment.
This tool initiates an enrichment operation via HTTP POST, creating an asynchronous job that modifies or augments contact records with additional data. It is a Write operation as it creates/updates enriched data in the system. The blast radius is medium since it affects contact records and may trigger external data lookups, but it does not delete data or involve financial transactions.
From the tool's definition POST /v1/contact/enrich — starts an enrichment job for contacts by LinkedIn URL or name+domain, returns a job_id (async, 202)
Attacks that exploit this kind of access
POST /v1/contact/enrich. Enrich specific contacts by LinkedIn URL or name+domain. Returns a job_id (async, 202). It is categorised as a Write tool in the DataMerge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DataMerge MCP server in PolicyLayer and add a rule for contact_enrich: 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 DataMerge MCP. Nothing to install.
contact_enrich is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the contact_enrich 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 contact_enrich. 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.
contact_enrich is provided by the DataMerge MCP server (poolside-ventures/datamerge-mcp). 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 →