Activity and audit
What is recorded about an assistant's calls, what is left out and who can read it.
Every tool call, playbook and resource read is recorded before it runs, and kept permanently. MCP activity shows where to read the record.
What is recorded
| Kind | Records |
|---|---|
| Calls | Each tool call, playbook and resource read: the tool, its arguments, the site, the outcome, how long it took and the client's name |
| Sign-ins | Refused requests: a revoked or expired token, an address outside the allow-list |
| Token changes | A grant created, connected, renamed, edited or revoked, and the work a grant's end stopped |
| Secrets | A secret page opened, shown, declined or expired, and a secret given to the assistant |
Each entry also keeps the token or app, the person it acted as and the IP address.
A call's outcome is Succeeded, Refused, Failed, Running or Ended early.
What is never recorded
- A secret's value, however it was delivered.
- Passwords, tokens and keys in arguments: they are replaced with
[redacted]. - Credentials the server recognises inside commands and error messages.
Redaction is best effort. Do not put a secret in a command when a tool argument or a deployment variable can carry it.
Who can read it
Every user of the organisation sees every entry, for every person's tokens and apps. No email is sent for any entry.
Was this helpful?