Session · proxy mode · with scenario
A real client, a real server, altered on the wire
client config → kymograph run --scenario poison-and-observe.yaml --on-rule-error continue --out-dir runs -- notes-server
The client started Kymograph in the server’s place, from its own config. Our stdout is the protocol channel. What this recording shows is one session as it happened — evidence of effect, and by its nature not repeatable.
state
complete
exit code
0 · the server’s
Proof of effect
- #5 poison-descriptions appended the canary instruction to 5 tool descriptions
- #7 the client’s next request carried
MCP-KYMOGRAPH-CANARYinparams.arguments.body
The injected text reached the consuming side, and this is what it then did. Whether a model obeyed is the client’s business; the wire shows the effect.
rule_quarantined
drop-list-changed raised at #12. With continue only that rule is stilled; the others keep working.Its drop at #6 is now invalid too: a rule that broke once cannot be trusted to have been right earlier.
authorization
{"target_declared": "localhost",
"engagement_confirmed_flag": false,
"scenario": "poison-and-observe",
"scenario_digest": "sha256:a81f…2c05"}
Stored as what they are: a declared target never verified, and a flag. Over stdio the target is the local child — the gate held.
Messages, both directions
→ client to server · ← server to client#{{sel.seq}} · {{sel.label}}
{{sel.tag}}{{sel.detail}}
{{sel.note}}