Docs

Destructive checks

MPP-13 closes a payment channel. The settlement is final, the channel can never be reopened, and no later check can run against it.

It is skipped by default in both front ends. Running it requires two independent things:

  1. An explicit opt-in on the process — --allow-destructive on the CLI, or WASIT_ALLOW_DESTRUCTIVE=1 / --allow-destructive when starting the MCP server.
  2. A named channel the run is permitted to close, which must match the channel the target advertises in its own 402 challenge.

Neither alone is enough.

Over MCP the destructive path is a separate tool, registered only when the opt-in is present at process start. Without it, wasit_mpp_channel_test_with_close does not appear in tools/list at all. This is deliberate: an allowDestructive: true parameter would be a boolean an agent could set for itself, which is not human consent in any meaningful sense. An agent cannot invoke a tool it cannot see.