send_datahub_events
Use this when the user wants to send DataHub events for ingestion (1–50,000 events per call). Each event requires a provider name and an RFC 3339 timestamp, and can optionally include dimensions and metrics. The API validates the entire request atomically, including duplicate event IDs anywhere i...
This record as markdown: /tools/doit/send-datahub-events.md
What send_datahub_events does on Doit
AI agents use send_datahub_events 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 |
|---|---|---|---|
events | array | Yes | Array of DataHub events to ingest (required). Each event requires a provider and time. Accepts 1 to 50,000 events per call. |
Parameters from the server's own tool schema.
Why send_datahub_events is rated Medium
An AI agent can call send_datahub_events 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.
Risk signalsHigh parameter count (11 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs send_datahub_events 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 send_datahub_events, this is the rule to start with:
send_datahub_events 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every send_datahub_events call is checked against it from then on.
Questions about send_datahub_events
Use this when the user wants to send DataHub events for ingestion (1–50,000 events per call). Each event requires a provider name and an RFC 3339 timestamp, and can optionally include dimensions and metrics. The API validates the entire request atomically, including duplicate event IDs anywhere in the request; a validation failure rejects the whole request. Success means accepted for asynchronous processing, not that records are already queryable. No processing latency is guaranteed. Do NOT use this for creating datasets (use create_datahub_dataset) or viewing datasets (use list_datahub_datasets). 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.
send_datahub_events accepts 1 parameter: events. Required: events. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for send_datahub_events: 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.
send_datahub_events is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_datahub_events 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.
Set action: deny in the PolicyLayer policy for send_datahub_events. 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.
send_datahub_events 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.
More on Doit, and thousands of servers like it.
This server
Across the catalogue