Skip to main content
Every tool call flows through the Tool Hub. This creates a natural chokepoint for logging—a complete audit trail of what happened, who did it, and why.
What gets logged
The request itself: timestamp, user identity (from IDP token), session ID, which tool was called, which connector provided it, what arguments were passed.
Access control decisions: was access allowed or blocked, which layer blocked it (if any), which role granted access, what origin the request came from.
Guardrail results: which guards ran, what they found, what action was taken, what was redacted (if anything).
Approval events: was approval required, who approved (or denied), when, with what justification.
The response: what the tool returned, how long execution took, any errors.
Sensitive content (PII, secrets) is redacted in logs according to your guardrail configuration. You get the audit trail without storing the sensitive data itself.
Retention and immutability
Logs are retained according to your configuration—30 days, 90 days, a year, whatever compliance requires.
Immutability prevents deletion during the retention period. Even admins can’t purge logs before retention expires. This matters for compliance regimes that require tamper-proof audit trails.
Redaction delay lets you keep full logs briefly (for debugging) then automatically redact sensitive fields after a window.
Export and integration
Logs can stream to your existing infrastructure:
SIEM integration sends logs to Splunk, Datadog, Elastic, or any system that accepts webhooks. Security teams see Char activity alongside everything else they monitor.
Compliance exports generate reports for audits—who accessed what tools, all approval decisions, guardrail violations, user activity summaries.
Query API lets you search logs programmatically. Find all L2+ approvals in the last 24 hours, all guardrail violations for a specific user, all tool calls from a specific origin.
Why centralized logging matters
Without the Tool Hub, audit trails are fragmented. Each MCP server logs its own calls, each application logs its own activity. Correlating across systems is painful.
With the Tool Hub as a single enforcement point, you get one audit trail covering all tool access—internal APIs, external services, browser extension tools, autonomous execution. One place to query, one format to parse, one integration to maintain. 
