You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The K8s logging guide claimed `outcome` was `success` or `failure`.
toolhive/pkg/audit/event.go defines five values, all reachable in
Kubernetes audit chains. #5872 also makes `denied` newly reachable on
MCPServer and MCPRemoteProxy by moving audit ahead of authorization so
Cedar denials no longer short-circuit before audit runs. The vMCP audit
guide was missing `application_error`, which the shared auditor emits
by default when a JSON-RPC response reports an error.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|`time`| string | Timestamp when the log was generated |
231
+
|`level`| string | Log level (`AUDIT` for audit events) |
232
+
|`msg`| string | Always "audit_event" for audit logs |
233
+
|`audit_id`| string | Unique identifier for the audit event |
234
+
|`type`| string | Type of MCP operation (see event types below) |
235
+
|`logged_at`| string | UTC timestamp of the event |
236
+
|`outcome`| string | Result of the operation: `success`, `failure`, `error`, `denied` (authorization denial), or `application_error` (transport succeeded but the JSON-RPC response reported an error)|
237
+
|`component`| string | Name of the MCP server |
238
+
|`source`| object | Request source information |
239
+
|`source.type`| string | Source type (e.g., "network") |
240
+
|`source.value`| string | Source identifier (e.g., IP address) |
0 commit comments