Tool Audit Trails
A complete, tamper-proof record of every action your agents take — which tool, on whose behalf, with what inputs and what result — so any question about what happened has an answer.
Think of the security-camera log in a store. On a normal day, nobody watches it. But the day something goes missing, you rewind to the exact minute and see what happened — instead of arguing about it. Audit trails are that camera, pointed at everything your AI agents do.
The problem, in plain words
An agent that acts on real systems — issues a refund, changes a record, sends a message — will eventually do something a human needs to look into. A customer disputes a charge. A compliance officer asks who accessed a file. A teammate swears the agent did it, not them. If the answer is scattered across half a dozen logs, some incomplete and some missing, the investigation takes days, eats your best people, and ends in a shrug. A shrug is a terrible answer to give an auditor.
What we set up
The registry — the gate every tool call passes through (built on MCP, the standard for agent tools) — writes one record per action, called a span. It captures the whole story: which tool was called, by which agent, on behalf of which person or client (the principal), with which permissions, with what inputs, what came back, whether it succeeded, and which larger job it belonged to (the parent trace). Sensitive details are redacted — blacked out — according to rules set per tool. The records are immutable (once written, nobody can edit them), kept for a defined retention period, and here is the part auditors love: reading the log is itself logged.
How it works, step by step
- Every action writes a record
No exceptions and no forgotten corners — if an agent did it through a tool, it is on the record.
- The record tells the whole story
Who, what, for whom, with which permissions, with what result — and a link to the larger job it was part of.
- Sensitive details are blacked out
Redaction rules apply per tool and per permission level, so the record proves what happened without exposing what it shouldn't.
- Records cannot be edited afterward
Storage is immutable with a governed retention period. What was written is what happened.
- Even reading the log leaves a trace
Access to the audit trail is itself audited — the camera also films the people reviewing the tape.
What changes for you
Before: 'what did the agent do, and on whose behalf?' launched a multi-day archaeology project. After: it is a query answered in minutes. Compliance reviews stop being a special event, because the evidence is already organized. Customer disputes about what the agent did get settled with a record, not a recollection. What it won't do: a trail records what happened — it does not stop a bad action from happening in the first place. Prevention is the job of permissions and human approvals; the trail is what makes everything they let through accountable.