MCP audit logging and privacy

The site records MCP and OAuth activity so administrators can investigate access and changes.

Recorded fields

An audit entry includes the UTC timestamp, acting WordPress user ID when available, authentication type, OAuth client ID when present, action name, status, redacted request and response summaries, and a one-way hash of the request IP.

The logger recursively replaces values whose keys look sensitive. Long strings are truncated after 600 characters. This reduces exposure but is not a substitute for input minimization: a secret placed under an unexpected key or inside ordinary prose may not be recognized.

The configured log-retention period defaults to 30 days and cannot be set below one day. Cleanup removes entries older than that period along with expired or revoked OAuth records.

Integration guidance

• Use clear client IDs and separate service identities.
• Keep secrets and unnecessary personal data out of arguments.
• Do not rely on the audit log as a content backup.
• Restrict diagnostics access to authorized administrators.
• Share only redacted action, time, status, and stable error codes with support.

POM AI’s audit log covers the site-local MCP server. The external AI client may keep its own history under a separate privacy policy.

Related guides: privacy, safe support information, and MCP authentication.