run_company_enrichment · DataMerge MCP: Risk & Policy

WHAT IT DOES

What run_company_enrichment does on DataMerge MCP

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

WHY IT NEEDS A POLICY

Why run_company_enrichment needs a policy

This tool triggers external enrichment operations on the DataMerge API with effects that depend on user-supplied arguments. While not destructive or financial, it executes jobs and processes whose outcomes are not immediately reversible or predictable. It goes beyond simple data retrieval (Read) as it actively initiates background operations.

From the tool's definition Tool 'run_company_enrichment' starts enrichment jobs and performs server-side polling operations. The description states the server 'starts the job and polls internally', indicating execution of external operations (enrichment processes) whose effects depend…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_company_enrichment Rate-limited

run_company_enrichment 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": {
    "run_company_enrichment": {
      "limits": [
        {
          "counter": "run_company_enrichment_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 run_company_enrichment

What does the run_company_enrichment tool do? +

Agent-friendly company enrichment. On the first call provide enrichment params (domain, domains, company_name, country_code, etc.); the server starts the job and polls internally for up to ~${RUN_JOB_DEFAULT_MAX_WAIT_SECONDS}s. If the job is still running, the response will be {status:. 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 run_company_enrichment? +

Register the DataMerge MCP server in PolicyLayer and add a rule for run_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.

What risk level is run_company_enrichment? +

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

Can I rate-limit run_company_enrichment? +

Yes. Add a rate_limit block to the run_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.

How do I block run_company_enrichment completely? +

Set action: deny in the PolicyLayer policy for run_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.

What MCP server provides run_company_enrichment? +

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