Skip to main content
Audit tools provide access to the Dome Platform audit trail. Query events by type, agent, or time range, inspect individual events, and export records for external analysis. These 4 tools require workspace context. Tool results render enum fields as short tokens (governing, denied, gateway_mcp), and filter arguments accept those same tokens. Refer to Enum rendering reference.
Audit reads are scoped to the active workspace. The server checks the workspace-level audit.view permission, so a workspace member can read their own workspace’s audit even without a tenant role. Tenant- or org-scoped API keys reading without a workspace context fall back to the tenant-level audit.view.

Audit Query

dome_audit_query Query audit events with optional filters. Returns events with type, agent, timestamp, and data. Permission: audit.view
Example tool call
Returns events in reverse chronological order. Each event includes an ID, type, timestamp, actor, and event-specific details.

Audit Get Event

dome_audit_get_event Get a single audit event by its ID. Permission: audit.view
Example tool call
Returns the full event record including all metadata, the acting principal, and the complete event payload.

Audit Export

dome_audit_export Export audit events in a SIEM-friendly format for external processing or archival. Supports the same filters as dome_audit_query, plus a format selector. Permission: audit.export
Example tool call
The same format set is available on dome audit export --format and on the file-based export connectors in Export Data.

Audit Usage

dome_usage Show LLM token consumption and a per-class estimated cost for the active workspace over the last 24 hours. Use it when an assistant needs to summarize workspace spend, build a budget guardrail, or confirm token attribution. This tool takes no parameters — it always reports the active workspace over the last 24 hours. For dimensional breakdowns (per-agent, per-API-key, per-identity, per-model), read the REST query surface directly. Permission: audit.view
Example tool call
Returns the workspace token summary as JSON:
The estimated cost is a blended cross-model rate intended for trend-watching, not a billable figure. Refer to Token Usage and Cost for the full token-class breakdown.

Next steps

Prefer the Operate how-tos for query patterns. This page is the tool surface: