Privacy-safe guild audit logs

The audit-logs toolset is read-only and requires Discord's View Audit Log permission in each permitted guild. Discord retains audit entries for 45 days. list_guild_audit_entries returns at most 50 entries newest first, accepts exact actor and numeric action filters, and requests one private lookahead entry so hasMore and nextBeforeEntryId are evidence-backed rather than guessed. get_guild_audit_entry uses Discord's ascending after semantics with the exact predecessor snowflake, then requires an exact identifier match. A missing entry returns found: false; a neighboring entry is never returned as the requested one. See Discord's audit log reference.

Every entry exposes its ID, a timestamp derived locally from that snowflake, numeric action type, a known stable action name or null for a future value, nullable actor ID, safe bounded change and option keys, counts, and reason presence. Change values and option values are always omitted. Discord's response also embeds users, webhooks, integrations, threads, application commands, scheduled events, and AutoMod rules; the connector ignores all of them. Because target_id can hold an invite code or another non-snowflake identifier, only valid snowflake targets are returned and all other non-null targets are marked as redacted.

Reasons are Discord content and are absent unless includeReasons or includeReason is explicitly true. The result identifies the active privacy tier. Audit responses are not cached, written to the local activity log, stored in operation receipts, used as telemetry labels, or otherwise persisted. Strict bounds, unique IDs, documented sort order, cursor direction, and requested actor and action filters are validated before any result is returned. This Discord server history remains separate from list_activity, which reports only this connector's own content-free local write records.

Canonical source: docs/reference.md