Failure Path Behaviour
When a downstream system is unreachable the gateway returns an explicit unavailable state. The agent surfaces that honestly — it does not fill the gap with a plausible answer.
Downstream system control
Take any MCP server down and watch dependent agents refuse to guess
mcp://crm-core.svc:8443 · eu-west-1
mcp://billing-edge.svc:8443 · eu-west-1
mcp://data-core.svc:8443 · eu-central-1
mcp://netops.svc:8443 · eu-west-1
mcp://servicedesk.svc:8443 · us-east-2
mcp://identity-vault.svc:8443 · eu-central-1
Honest refusals
Calls that hit an unavailable upstream
No failure-path events
Take a system down above, then inject a call routed to it.
Call trail
Select any call in the live stream to open its full trail
No call selected
Click a row in the live MCP flow to inspect identity, policy decision, token and result.
Component state contract
What each screen renders in every condition — no fabricated placeholders
Skeleton or streaming indicator while the gateway responds.
Grounded result returned from the governed backend.
Empty result stated as empty — never padded.
Explicit failure with the rule or fault that caused it.
Upstream unreachable — the agent answers “I don't know”.
All systems simulated · no live integrations