POST /v1/company/enrich. Enrich one or more companies by domain. Returns a job_id (async). Single: domain. Batch: domains, country_code, global_ultimate, list, skip_if_exists.
AI agents invoke start_company_enrichment to trigger actions in DataMerge MCP. 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.
This tool initiates an asynchronous external enrichment job against the DataMerge API. It is not a simple read (it POSTs and causes side effects), not purely a write of user-controlled data, and not destructive or financial. It executes an external process that consumes API credits and potentially modifies company records or lists, placing it in the Execute category.
From the tool's definition POST /v1/company/enrich — triggers an enrichment job (async), returns a job_id; described as starting an external operation whose effects depend on arguments (domain, batch options, list assignment)
Attacks that exploit this kind of access
POST /v1/company/enrich. Enrich one or more companies by domain. Returns a job_id (async). Single: domain. Batch: domains, country_code, global_ultimate, list, skip_if_exists. It is categorised as a Execute tool in the DataMerge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DataMerge MCP server in PolicyLayer and add a rule for start_company_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 DataMerge MCP. Nothing to install.
start_company_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 start_company_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 start_company_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.
start_company_enrichment 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 →