The stop line reads what each action touches, not which command spells it. A delete outside the bot’s folder stops, whether it’s rm, a Finder script, a force push, a dropped database table or a delete through a connected app. A payment stops whether it goes through a connected app or a shell call to a payment API.
A first message to someone new stops. A reply in a conversation you already have goes ahead on Auto and Full access. When it can’t tell where an action lands, it stops: a wrong stop costs you one card. A bot reading your keys or saved passwords stops on every level, No limits included.
It’s a classifier, not a sandbox, and it’s table-tested: more than 100 cases in server/stop-line.test.ts, plus tests for real misses we’ve found and fixed.
It judges the permission requests that reach Murage, so what it covers depends on the engine. On Claude Code and Codex, the stop line also covers tools from MCP servers you add. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about. For Hermes, that is every tool except reads, searches and its own memory, including MCP and connected-app tools.