Auditability

Know what was accessed, why, and under whose authority.

Trace agent access across enterprise data and systems. Review the identity, operation, and outcome, with request context to investigate the work behind it.

Governed data access runtime

Evidence for oversight and investigation.

CISOs and security teams need evidence of how enterprise data is being used. Trace the authority, data access, and actions behind agent activity across connected systems.

What was accessed

Identify the connected system and data operation involved in a request, with query details where available.

auditabilitylive
connectionsnowflakeoperationqueryobjectledger.entriesfiltervendor_id = 4471rows36
data.accesssdk

The system, the operation, and the query details where available

req#a91cactivity history · export

Under whose authority

Associate activity with the user or agent identity under which access was authorized.

auditabilitylive
useramina@acmeagentsvc:agent-42delegated viaclaude.aipermissionfinance_readagent policyread only
authority.resolvedmcp

Every request tied to the identity that authorized it

req#a91cactivity history · export

For which task

Use supplied task or request context to connect access to the work it served. Administrators can inspect operations and outcomes and export activity for review.

runtime · activity historylive
$ activity list --agent svc:agent-42 --since 24h09:14  query   snowflake.ledger      allowed09:15  read    salesforce.account    allowed09:15  update  payments.vendor       denied$ activity export --format csv✓ exported for review▍
From operation to evidence

Follow the access behind an answer.

Use activity records to investigate how an agent reached enterprise data. Review the recorded operations alongside the task and the access it was meant to have.

  1. Find the identity and operation

    Review when an operation ran, the MarcoPolo identity and connection involved, its action, and its outcome. Depending on the operation, details can include query text, tool name, row count, and duration.

  2. Inspect the request context

    Examine the associated trace and any saved query files or artifacts. Use the supplied task or request context to understand the work; an activity record does not infer a business purpose that was never supplied.

  3. Bring evidence into security review

    Administrators can review organization activity and export the events shown. OpenTelemetry logging and tracing bring these operations into existing monitoring and SIEM tools.

Illustrative activity record

A ledger read during an investigation.

Workspace identity
Payments analyst
Connection
Ledger database
Operation
Query transaction references, amounts, and dates.
Outcome
Read completed.

Tool response payloads are not captured in traces by default. Capturing the exact data returned requires a separate decision about response capture, redaction, access, and retention.

Make the first run reviewable.

Walk through an operation, the evidence it leaves, and how your team will use it for investigation and oversight.