MCP Server Security

MCP audit logging: what to record

An MCP audit log should record every tool invocation with its full parameters, the user, the client, the server and version, the decision taken and a timestamp, with secrets redacted, and export it to a SIEM. No MCP document sets a retention period, so set one and check any vendor's default. Sources were read on 16 Nov 2026.

Facts read on .

Which fields belong in an MCP audit log?

Log enough to answer who called which tool on which server with what arguments and what happened. OWASP's cheat sheet asks for all MCP tool invocations to be logged with full parameters, user context and timestamps.

Add the context an investigator needs:

Sources: OWASP MCP Security Cheat Sheet.

How long should logs be kept?

Keep them as long as your own policy or regulation requires; none found on 16 Nov 2026 in the MCP specification or the OWASP cheat sheet, which set no retention period. Products differ, so read each default.

Snyk's documentation, for example, lists a fixed seven-day data retention for its Agent Behavior Governance, which means a team that needs a longer record must export the data.

Write the retention period into policy for each log tier, for example raw parameters for a short period and summaries for longer, so the record you keep matches the questions an auditor will ask.

Sources: OWASP MCP Security Cheat Sheet; Snyk documentation: Agent Behavior Governance; Snyk documentation: MCP Governance.

What should you redact from MCP logs?

Redact secrets and personal data before the record is stored. OWASP says logs should have secrets and PII removed, which matters because tool arguments often carry tokens, file contents and customer data.

Keep tokens out of configuration and logs altogether: OWASP advises using the operating system's credential store rather than plaintext config files.

Decide who may read the logs. Full parameters are sensitive by nature, so restrict access to the security team and write the redaction rules before the first record is stored, not after the first incident.

Sources: OWASP MCP Security Cheat Sheet.

Where should MCP logs go?

Send them to the system your analysts already use. OWASP recommends feeding MCP logs into a SIEM for anomaly detection. Tools document several routes: Cisco's DefenseClaw lists OTLP, Splunk, file and webhook destinations, CrowdStrike says Guardian exports agent telemetry into Falcon Next-Gen SIEM, and Harmonic Security's documentation describes full invocation logs with parameters and responses.

Lasso Security says it exports audit trails of every MCP connection and tool call to a SIEM; Bay says events reach a SIEM in OCSF format. These are vendor statements.

Test the pipeline with a deliberate blocked call and confirm it reaches the SIEM with every field intact.

Sources: OWASP MCP Security Cheat Sheet; Cisco DefenseClaw documentation: observability; CrowdStrike: Falcon Guardian defines next generation of AI security; Harmonic Security documentation: What is the MCP Gateway; Lasso Security: MCP security use case; Bay: AI agent investigation.

Which alerts are worth setting on MCP activity?

Alert on change and on volume. OWASP lists new tools being called, admin-level queries and abnormal call frequency, and asks teams to monitor for credentials from one server appearing in calls to another.

Add an alert for any tool definition whose hash differs from the reviewed one, since that is the rug pull signal.

Sources: OWASP MCP Security Cheat Sheet.

Can you trust a log you did not build?

Treat it as evidence to be judged, not as proof. OWASP points readers to a separate cheat sheet on verifying third-party agent execution evidence for exactly this case.

When the log comes from a vendor, check what it establishes: whether the record is created before or after the action, who can edit it and whether you can export it in full.

Sources: OWASP MCP Security Cheat Sheet.

Sources