browser_responses_stop

What browser_responses_stop does on Termux Browser Pilot

AI agents invoke browser_responses_stop to trigger actions in Termux Browser Pilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why browser_responses_stop is rated High

This tool modifies the runtime behavior of the browser automation system by halting response body capture. While not destructive (the capture can be restarted) and not a direct read/write of persistent data, it is an Execute category action because it controls an active process/daemon behavior whose effects depend on prior state and whose misuse could interfere with browser operations or hide/modify data flows.

From the tool's definition Tool name 'browser_responses_stop' and description 'Stop capturing response bodies (stops re-injection)' indicate active control over browser response capture behavior—a state-changing operation on the browser automation daemon.

The rule that runs browser_responses_stop safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Termux Browser Pilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_responses_stop, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_responses_stop": {
      "limits": [
        {
          "counter": "browser_responses_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about browser_responses_stop