browser_console_start
Start capturing browser console output (log, warn, error, info).
This record as markdown: /tools/salviz-termux-browser-pilot/browser-console-start.md
What browser_console_start does on Termux Browser Pilot
AI agents invoke browser_console_start 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_console_start is rated High
This tool initiates an active process/operation in the browser daemon — starting a capture session that hooks into browser internals. While it primarily reads console output, 'Start capturing' implies triggering a persistent side-effecting operation (starting a monitoring process) rather than a simple read. It falls under Execute as it initiates an ongoing browser operation.
From the tool's definition Start capturing browser console output (log, warn, error, info)
Attacks that exploit this kind of access
The rule that runs browser_console_start 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_console_start, this is the rule to start with:
browser_console_start stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_console_start call is checked against it from then on.
Questions about browser_console_start
Start capturing browser console output (log, warn, error, info). It is categorised as a Execute tool in the Termux Browser Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_console_start: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Termux Browser Pilot. Nothing to install.
browser_console_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_console_start rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for browser_console_start. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
browser_console_start is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Termux Browser Pilot, and thousands of servers like it.
Across the catalogue