run_contact_enrich · DataMerge MCP: Risk & Policy

WHAT IT DOES

What run_contact_enrich does on DataMerge MCP

AI agents invoke run_contact_enrich 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_contact_enrich needs a policy

This tool executes an enrichment job whose effects depend on the contacts and fields provided by the agent. It triggers external API operations (DataMerge Company API) and maintains polling state. While not destructive or financial, it runs an operation with side effects on an external system.

From the tool's definition Tool name contains 'run_' prefix indicating action execution; description states it 'starts the job and polls internally', demonstrating active job initiation and external operation triggering.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_contact_enrich Rate-limited

run_contact_enrich 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_contact_enrich": {
      "limits": [
        {
          "counter": "run_contact_enrich_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_contact_enrich

What does the run_contact_enrich tool do? +

Agent-friendly contact enrichment. On the first call provide contacts and enrich_fields; the server starts the job and polls internally for up to ~${RUN_JOB_DEFAULT_MAX_WAIT_SECONDS}s. If still running, returns {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_contact_enrich? +

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

What risk level is run_contact_enrich? +

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

Can I rate-limit run_contact_enrich? +

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

How do I block run_contact_enrich completely? +

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

What MCP server provides run_contact_enrich? +

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