DPO Radio

MCP Audit & Observability

Overview Image

Why MCP Audit & Observability Matter

When a regulator asks "what did the AI integration do last quarter?", the customer needs a defensible answer. A summary export from an external AI vendor is not enough. The auditor wants the call-by-call trail: which integration, which tool, which arguments, which record, who approved, when, and what the outcome was.

Forseti's MCP traffic flows through the same Immutable Audit Trail (IAT) as the rest of the platform. The same chain-of-custody anchor protects every Forseti event, including every MCP call. The Audit Trail page carries a Source filter chip that isolates MCP traffic with a single click, so the auditor (or the country compliance manager doing a pre-audit pass) can walk the full external-integration history in minutes.

The proof tap is nightly and tamper-evident. Auditors can verify the chain end to end and confirm that no event has been silently removed. The lineage view stitches read calls, write proposals, approvals, executions, and downstream record changes together by shared identifiers, so any AI-touched record can be traced back through the full external-integration history.

How It Works

Every Call Emits a Canonical Audit Event

Every read tool call emits an "AI advisor tool called" event with an explicit MCP source marker, the requesting key prefix, the tool name, the arguments, the latency, and the outcome. Write proposals emit five lifecycle events — proposed, approved, executed, declined, expired — stitched together by a shared proposal identifier.

Source Filter Chip on the Audit Trail Page

The Audit Trail page carries a Source filter chip with values that include Forseti and MCP. Selecting MCP isolates external-integration traffic. Selecting Forseti shows the in-product chat and workflow traffic. The two can be combined with other filter chips (record type, time window, persona, key prefix).

Per-Key Audit Subview

Each MCP key carries its own audit subview that shows every call made with the key, the timeline, the tool mix, the average latency, and the outcome distribution. The subview is the canonical surface for revocation hygiene — an administrator reviewing whether to rotate or retire a key looks here first.

Lineage Stitching for AI-Touched Records

Any AI-touched record carries a lineage trail that stitches together the read calls, write proposals, approvals, executions, and downstream changes by shared identifiers. The Forseti Audit Lineage view walks the chain from the originating call through every committed change.

Tamper-Evident IAT Proof Tap

The platform's Immutable Audit Trail emits a tamper-evident hash chain nightly. Auditors can verify the chain end to end and confirm that no event has been silently removed. The same anchor protects every Forseti event, including every MCP call, every approval-queue lifecycle event, and every linked downstream change.

Regulator-Pack Export

Audit-trail rows export through the platform's unified export pipeline for regulator handoff. The export carries tool name, arguments, requesting key prefix, latency, outcome, and the source marker. The country compliance manager hands the inspector a complete external-integration trail rather than a reconstructed narrative.

The Difference

Graphic Image

Without IAT-Backed MCP Audit

Graphic Image

With Forseti MCP IAT Audit

IconExternal AI integration traffic lives in the vendor's logs, not in the compliance platform.
IconEvery MCP call, proposal, approval, and execution flows through the same Immutable Audit Trail as the rest of the platform.
IconThe audit story for any AI-initiated read or write is reconstructed across two systems.
IconThe Source filter chip isolates MCP traffic on the Audit Trail page in one click.
IconTamper-evident verification of the audit chain is not available.
IconPer-key audit subview is the canonical surface for revocation hygiene.
IconA regulator asking "what did the AI do?" gets a vendor summary, not a customer-controlled trail.
IconThe lineage view walks AI-touched records from originating call through every committed change.
IconPer-key revocation hygiene is impossible without per-key call-by-call history.
IconThe IAT proof tap is tamper-evident and exported for regulator handoff.

Built for Auditable AI

Build For Image

The same chain-of-custody anchor that protects every other audit event in the platform protects every Forseti event, including every MCP call. The IAT is immutable; no audit event is silently removed or edited.

Build For Image

The lineage view stitches read calls, write proposals, approvals, executions, and downstream record changes by shared identifiers. Auditors can walk from the originating MCP call through every committed downstream change.

Build For Image

The nightly proof tap is tamper-evident. Auditors can verify the audit chain end to end and confirm that no event has been silently removed.

Overview Image

Follow a Scoped Connection's Activity

Use the connector audit history to inspect tool activity and the decision on a consequential proposal. Forseti audit lineage connects that activity with the broader review history where applicable.

Background Image

See MCP Audit & Observability in Action

Ready to see a quarter of external-integration traffic walked end to end through the Audit Trail page? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run a 30-day pilot of MCP integration and walk the resulting audit trail with your internal audit lead. Use the Source filter chip and the per-key audit subview.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how the IAT-backed audit fits your existing inspection-readiness posture.

Frequently Asked Questions About MCP Audit & Observability

Yes. The Audit Trail page carries a Source filter chip that includes an MCP value. Selecting it isolates external-integration traffic. The filter combines with other chips (record type, time window, key prefix) for deeper drill-down.

Each write proposal emits five lifecycle events — proposed, approved, executed, declined, expired — that share a single proposal identifier. The Audit Trail page and the Forseti Audit Lineage view walk all five events as one linked thread.

The per-key audit subview is the canonical surface. It shows every call made with the key, the timeline, the tool mix, the average latency, and the outcome distribution. Administrators reviewing revocation hygiene check the subview before deciding to rotate or retire.

Yes. The platform's Immutable Audit Trail emits a tamper-evident hash chain nightly. Auditors can verify the chain end to end and confirm that no event has been silently removed.

Yes. Audit-trail rows export through the platform's unified export pipeline. The export carries tool name, arguments, requesting key prefix, latency, outcome, and the source marker so the country compliance manager hands the inspector a complete external-integration history.