cdp_run_data_export

What cdp_run_data_export does on CDP MCP Server

AI agents invoke cdp_run_data_export to trigger actions in CDP MCP Server. 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 cdp_run_data_export is rated High

Data export operations execute processes that extract and move data out of the system. While not destructive or financial, the execution of an export process that could extract sensitive customer data from the CDP represents a meaningful blast radius if an AI agent misuses it (e.g., exporting without proper authorization, exporting to unintended destinations, or triggering resource-intensive operations).

From the tool's definition Tool name 'cdp_run_data_export' indicates execution of a data export operation. Coupled with context that this is part of a CDP administrative API with ~300 tools for managing tenants, campaigns, and workflows, the 'run' verb signals triggering an external…

The rule that runs cdp_run_data_export safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CDP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdp_run_data_export, this is the rule to start with:

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

Questions about cdp_run_data_export