What the Pipeline Captures
Request and Response Flow
Every request and response passes through the same set of observability layers, so nothing slips by unrecorded.Audit Guarantees
The audit layer is designed to block a successful operation if it can’t be recorded. This is a deliberate security choice: every completed MCP call must have a corresponding audit record, so compliance teams can rely on completeness. The other layers absorb errors silently — observability should never break your workflow.Beyond observability, the pipeline also enforces policy. Governance admission determines which tool calls are allowed, and Guardrails evaluate each request and enforce policy before it reaches the upstream server.