From the In-flight: the money moving through your Kafka architecture map
Cluster writes are off by default and pass one shared gate
Console, MCP and CLI redrive through Setup.redrive (Setup.java:29-33), refusing unless the queue belongs to the active flow (324-327), the engine is not sample data (328), and the running profile allows writes (331-334); that flag defaults to false (Workspace.java:171; Mcp.java:301). All three default to a dry run (Mcp.java:528, Api.java:145, Setups.java:249). A pass is rate-capped (Redrive.java:69), stops at the queue's end as of its start (105, 153), and skips letters already redriven (158).
Impact: A mistaken run is confined to one queue of the active flow, one pass and the rate cap, and nothing is written unless a profile was explicitly opened for writes.
The gate bounds where and how fast a run writes, not how many records match or who else reads the target topic; those are the open edges of the blast radius covered by the other findings. The redrive tool is only offered when the server runs from the workspace (Mcp.java:497), and writers exist only on adapters declaring the redrive capability (Redrive.java:97).