Audit tools | Made with Pepper Agent API

These read tools use the same event fields and permissions as Settings > Audit log. AI is optional. You confirm sensitive steps in Pepper; these tools cannot export customer data, erase personal fields, change retention or run verification.

List and open events

Tool	Inputs	Result
`audit.list`	Optional page, page size (25, 50 or 100), event, actor, from/to date, record type and record ID	Permitted events and pagination
`audit.get`	Event `id`	One permitted event, its covered facts and stored hash
`audit.integrity`	None	Last verification result, its date and the number of events waiting for a seal

MCP uses underscores in tool names, for example audit_list. HTTP uses GET /api/v1/audit/events, GET /api/v1/audit/events/{id} and GET /api/v1/audit/integrity.

The connection needs the Settings read grant. Its person also needs audit_log.view or audit_log.view_own to list or open events. Own-history access returns only that person's permitted events. Integrity needs audit_log.view. Current record access applies in every case. An owner cannot use this grant to see another person's private board.

Results include the event, actor, source record, time and covered business facts. A list-read event shows a count instead of sending every identifier to the client. Tools return no raw metadata, IP address, browser details or credentials. Losing record access removes the event, including a whole sampled batch if any referenced record is no longer accessible.

Read the integrity result honestly

A stored hash is not a fresh verification. Pending means new events need a seal. Stale means the last check is more than a day old. A client must keep those states visible instead of saying the entire log has been verified.

Open Audit log to check the history. The same guide explains hash coverage, partial signed exports, the limits of a local chain and personal-field erasure.

For local installation checks, use installation.health.