POST /v1/company/enrich then poll GET /v1/company/enrich/{job_id}/status until status is "completed" or "failed" or timeout. Same params as start_company_enrichment plus poll_interval_seconds and timeout_seconds.
Risk signalsAccepts URL/endpoint input (webhook_url) · High parameter count (11 properties)
Part of the DataMerge MCP server.
Free to start. No card required.
AI agents invoke start_company_enrichment_and_wait to trigger processes or run actions in DataMerge MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
start_company_enrichment_and_wait can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"start_company_enrichment_and_wait": {
"limits": [
{
"counter": "start_company_enrichment_and_wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full DataMerge MCP policy for all 23 tools.
These attack patterns abuse exactly the kind of access start_company_enrichment_and_wait gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
POST /v1/company/enrich then poll GET /v1/company/enrich/{job_id}/status until status is "completed" or "failed" or timeout. Same params as start_company_enrichment plus poll_interval_seconds and timeout_seconds.. 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_and_wait: 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_and_wait 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_and_wait 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_and_wait. 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_and_wait is provided by the DataMerge MCP server (https://mcp.datamerge.ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 DataMerge MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.