mcp-kymograph
recording schema 4 · rules v4
Stock-take · driver mode

What poison-server exposes

complete · exit 0
$ kymograph drive --manifest corpus.yaml --entry poison-server --isolation runc --out-dir runs
run
runs/20261008T081133-2be0
mode
driver · script discovery
transport
stdio · 2025-06-18 announced
isolation
runc · proof held
server exit
0 · recorded, never handed through
server_name_mismatch The server announces itself as weather-server; the entry is poison-server. Findings are keyed by the entry’s name — a server cannot borrow another’s.

The script, one turn at a time

lists, never acts — no tool is called, no resource read
  1. {{s.n}} {{s.step}} {{s.outcome}}
{"type": "step_skipped", "step": "prompts/list", "reason": "capability_not_offered", "detail": ""} {"type": "script_finished", "inventory": "complete"}
{{t.name}}{{t.title}}{{t.fields}}
{{p.text}}
{{h}}
{{r.uri}}{{r.name}} · {{r.mime}}
{{template}}Station by city · application/json
Not offered — not asked. The server’s initialize answer had no prompts capability, so prompts/list was not sent. That is a different statement from “the server has no prompts”, and the recording keeps them apart.

run_finished — the account

observations · tools/list
5
observations · resources/list
0
findings · all-signals
4 (pinned: 4)
server_redactions
1
inspection_bounded
0
quarantined_rules
[]

Written on the one path that cannot drop it. inspection_bounded exists so a run gone quiet for lack of budget cannot read like a run that found nothing.

States and exit codes

complete0a result refused2nothing started incomplete3data is missing server_failed4nothing observed sandbox_failed5isolation did not hold output lost74stdout closed interrupted130Ctrl-C, no run to record it