datahub_import_provider_records

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 75 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/datahub-import-provider-records.md

WHAT IT DOES

What datahub_import_provider_records does on Doit

AI agents use datahub_import_provider_records to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.

Parameter	Type	Required	Description
`records`	array	Yes	One object per source row; keys are the template's CSV column names. Decimals may be strings or numbers.
`replace`	boolean	—	Same semantics as the `replace` field of the CSV upload.
`provider`	string	Yes	Existing dataset (provider) name.
`periodEnd`	string	Yes
`periodStart`	string	Yes
`schemaTemplate`	string	Yes	Versioned schema template of the records.
`customerContext`	string	—	Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.

Parameters from the server's own tool schema.

RISK

Why datahub_import_provider_records is rated Medium

An AI agent can call datahub_import_provider_records faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs datahub_import_provider_records safely

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

datahub_import_provider_records Rate-limited

datahub_import_provider_records stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "datahub_import_provider_records": {
      "limits": [
        {
          "counter": "datahub_import_provider_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every datahub_import_provider_records call is checked against it from then on.

FAQ

Questions about datahub_import_provider_records

What does the datahub_import_provider_records tool do? +

Ingest third-party cost, usage, and metric-based data for analysis. Sends provider-native records as JSON instead of a CSV file. The records use the same columns as the template's CSV (currently anthropic-spend-report@1 only) and are validated, normalized and booked on periodEnd exactly like a CSV upload. It may take up to 15 minutes for the data to become available in the DoiT console. It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does datahub_import_provider_records accept? +

datahub_import_provider_records accepts 7 parameters: records, replace, provider, periodEnd, periodStart, schemaTemplate, customerContext. Required: records, provider, periodEnd, periodStart, schemaTemplate. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on datahub_import_provider_records? +

Register the Doit MCP server in PolicyLayer and add a rule for datahub_import_provider_records: 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 Doit. Nothing to install.

What risk level is datahub_import_provider_records? +

datahub_import_provider_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit datahub_import_provider_records? +

Yes. Add a rate_limit block to the datahub_import_provider_records 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 datahub_import_provider_records completely? +

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

datahub_import_provider_records is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →