Which BI tools log what outside agents did?

Quoted from Databricks’s docsSecurity and compliance: Every span records the requester identity, endpoint name, and full request payload, so you can feed it into your security tooling for threat detection and investigation.

Quoted from Snowflake’s docsTogether, these columns help you reconstruct the causal chain that compliance teams often need: a user invoked an agent, specific queries followed, and specific objects were accessed.

Quoted from Omni’s docsRetrieve the full result of a completed AI job, including all actions taken by the AI (queries generated, data retrieved) and the final summarized answer.

Quoted from Hex’s docsThis view lets you review individual turns in the conversation, inspect tool calls made by the agent, and see the primary data assets referenced at each stage.

Quoted from Sigma’s docsAlso fires for Sigma MCP Server requests.

Quoted from BigQuery’s docsQueries executed using the execute_sql tool will always have the default job label goog-mcp-server: true automatically set in addition to any custom labels provided in the request.

Quoted from Looker’s docsEvery action taken by an AI agent is logged in Looker System Activity and Cloud Audit Logs.

Quoted from Power BI’s docsWhen you authenticate with a service principal (described next), the user ID captured by the activity log is the Application ID.

Quoted from Metabase’s docsThe Tool calls tab lists each call with its tool, client, user, status, duration, and error type.

Quoted from Alteryx’s docsActions performed by service principals appear in the Audit Log with: agent_type = SERVICE_PRINCIPAL

Quoted from MotherDuck’s docsQueries run by any end user are attributed to the service account that owns the token, not to the individual Microsoft 365 user.