Trust in an AI agent comes from one thing above all: being able to see exactly what it did. The Audit Log is NIBWP’s answer — a complete, timestamped record of every tool call made against your site. This guide shows how to read it, what to look for, and how to use it for security reviews, debugging and client reporting.
The Audit Log records every ability call — which tool, which token, the arguments, the result, the timing. Use it to review what agents did, debug failures, and prove work to clients. It is always on; nothing an agent does is invisible.
Open the Audit Log
Go to NIBWP › Audit Log. You will see a reverse-chronological list of calls. Each row is one tool invocation, with enough detail to reconstruct exactly what happened.
What each entry tells you
| Field | What it tells you |
|---|---|
| Tool | Which ability was called — e.g. wp-update-post |
| Token | Which client/agent made the call |
| Status | Success, refused (out of scope), or error |
| Timing | When it ran and how long it took |
| Result | What changed — the affected ID, the outcome |
Three ways to use it
The same log serves three jobs:
- Security review — after a bulk job, scan for anything unexpected. Refused calls show an agent reaching beyond its scope (and being stopped).
- Debugging — when a workflow fails, the log shows the exact call and error, so you fix the cause, not the symptom.
- Client reporting — export the log as a record of work done on a client site each month — your changelog and proof of work in one.
FAQ
Is logging always on?
Can I see refused calls?
Can I export it?
See everything your agents do
Every call, logged — review, debug and report with confidence.
Get NIBWP