browser_dialog_handle
A execute tool on the Termux Browser Pilot MCP server.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-dialog-handle.md
What browser_dialog_handle does on Termux Browser Pilot
AI agents invoke browser_dialog_handle 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_dialog_handle is rated High
The tool name suggests it handles browser dialogs (e.g., alert, confirm, prompt, file dialogs), which constitutes a browser action/interaction. Dialog handling can trigger external operations such as accepting file uploads, confirming destructive actions, or granting permissions.
From the tool's definition Tool name 'browser_dialog_handle' on a browser automation server (Termux Browser Pilot) that 'Runs Firefox or Chromium... with a persistent daemon'
Attacks that exploit this kind of access
The rule that runs browser_dialog_handle 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_dialog_handle, this is the rule to start with:
browser_dialog_handle 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_dialog_handle call is checked against it from then on.
Questions about browser_dialog_handle
browser_dialog_handle is a execute tool on the Termux Browser Pilot MCP server. 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_dialog_handle: 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_dialog_handle 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_dialog_handle 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_dialog_handle. 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_dialog_handle 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