From the In-flight: the money moving through your Kafka architecture map

The MCP recovery tools score about 40 of 100 for unattended agent use

observation · medium · inferred

Scored on this code: schema 70 (closed argument objects, Mcp.java:149, but catalog and patch are open objects, Mcp.java:365, 375); escape hatch 60 (dry run by default, stop, console confirm); blast radius 30 (self-granted writes, any target topic, any secret path); observability 25; provenance 30; identity 20 (no per-agent scope). Cost is the client's: no model runs inside. The read-only tools score far higher: annotated read-only, masked samples (Mcp.java:329).

Safe first moves: observe-mode agents on value_at_risk, stuck_events and impact, and augment-mode drafting with draft_catalog. Not yet: a real redrive, edit_catalog on an active flow, approve_change. First architectural move: make write authority something the person grants per action, not a profile field the agent can set.

The trail

  1. MCP Server
  2. Observer Facade
  3. Redrive
Open on the map

More from this board