datahub_events_csv_file

SERVERDoit SOURCE@doitintl/doit-mcp-server

Low RISK CLASS

Category Read

Parameters 70 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/datahub-events-csv-file.md

WHAT IT DOES

What datahub_events_csv_file does on Doit

AI agents call datahub_events_csv_file to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`file`	string	—	The CSV file to upload, either uncompressed or compressed in ZIP or GZ format. The maximum file size is 30 MB. (base64-encoded file content)
`replace`	boolean	—	Template uploads only. When `true`, active batches whose report period overlaps this upload are soft-deleted before the new file is ingested, and their ids are
`provider`	string	—	The identifier of the data provider. Allowed characters: alphanumeric (0-9,a-z,A-Z), underscore (_), space, dash (-).
`periodEnd`	string	—	Inclusive last day of the report period (YYYY-MM-DD). Events are booked on this day.
`periodStart`	string	—	Inclusive first day of the report period (YYYY-MM-DD). Required for template uploads whose filename does not carry the period; when both are present they must a
`schemaTemplate`	string	—	Versioned schema template of the file. Defaults to the dataset's template (`default@1` for datasets created without one). Provider-native templates such as `ant
`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_events_csv_file is rated Low

Even though datahub_events_csv_file only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts file system path (file)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs datahub_events_csv_file 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_events_csv_file, this is the rule to start with:

datahub_events_csv_file Allowed

datahub_events_csv_file is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "datahub_events_csv_file": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about datahub_events_csv_file

What does the datahub_events_csv_file tool do? +

Ingest third-party cost, usage, and metric-based data for analysis. Sends a batch of events to DataHub using a CSV file, either uncompressed or compressed in ZIP or GZ format. It may take up to 15 minutes for the data to become available in the DoiT console. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.

What parameters does datahub_events_csv_file accept? +

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

How do I enforce a policy on datahub_events_csv_file? +

Register the Doit MCP server in PolicyLayer and add a rule for datahub_events_csv_file: 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_events_csv_file? +

datahub_events_csv_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit datahub_events_csv_file? +

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

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

datahub_events_csv_file 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

get_file_snippet on ACE-MCP →read_input_file on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →