start_company_enrichment_and_wait

WHAT IT DOES

What start_company_enrichment_and_wait does on DataMerge MCP

AI agents invoke start_company_enrichment_and_wait 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.

WHY IT NEEDS A POLICY

Why start_company_enrichment_and_wait needs a policy

This tool executes an operation (company enrichment) on a remote service and waits for completion. While it doesn't directly modify stored data like Write, nor permanently delete like Destructive, it does trigger external processing and state changes on the DataMerge API. The enrichment job likely fetches and processes data, which qualifies as Execute.

From the tool's definition The tool description indicates it performs a POST request to start an enrichment job followed by polling GET requests to check status. This is an asynchronous operation that triggers external processing on a remote API.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_company_enrichment_and_wait Rate-limited

start_company_enrichment_and_wait stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_company_enrichment_and_wait": {
      "limits": [
        {
          "counter": "start_company_enrichment_and_wait_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DataMerge MCP, so you can run agents against it safely.

FAQ

Questions about start_company_enrichment_and_wait

What does the start_company_enrichment_and_wait tool do? +

POST /v1/company/enrich then poll GET /v1/company/enrich/{job_id}/status until status is. 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.

How do I enforce a policy on start_company_enrichment_and_wait? +

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.

What risk level is start_company_enrichment_and_wait? +

start_company_enrichment_and_wait is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_company_enrichment_and_wait? +

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.

How do I block start_company_enrichment_and_wait completely? +

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.

What MCP server provides start_company_enrichment_and_wait? +

start_company_enrichment_and_wait 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.