Skip to main content

Security 7 - Audit trail

When a gate or behaviour rule rejects a tool call, Digitorn keeps a trail you can review from the app session UI: what was attempted, when, and why it was refused.

What you look at as an app author​

PlaceWhat you see
Session transcriptThe tool call, the rejection / gate message, later turns
Session activity / events in the Digitorn UIOrdered tool and hook activity for that chat
Credential settings (operators)Who created or refreshed vault entries

You do not need HTTP tooling for day-to-day app debugging: open the session that failed and read the rejected tool call.

Reproduce a rejection​

Reuse custom-rule-bot from Security 3: a behaviour rule forbids writes under secrets/.

bash
digitorn install custom-rule-bot.yaml
digitorn chat custom-rule-bot

Ask the agent to write a file under secrets/. The rule blocks the call. In the session UI you should see the attempted filesystem.write and a refusal reason that matches your rule.

What to put in YAML for clearer audits​

  • Give hooks and behaviour rules stable id values.
  • Put a clear reason on deny / gate actions.
  • Prefer explicit tools.capabilities grants so unexpected tools never appear.