browser_window_list

List all open browser windows (main + popups).

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/salviz-termux-browser-pilot/browser-window-list.md

WHAT IT DOES

What browser_window_list does on Termux Browser Pilot

AI agents call browser_window_list to retrieve information from Termux Browser Pilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browser_window_list is rated Low

This tool only lists/enumerates existing browser windows. It performs a read-only query of browser state with no ability to modify, delete, or execute actions. The blast radius of misuse is minimal—an AI agent could at most observe which windows are open, which poses no direct security risk compared to other categories.

From the tool's definition Tool name 'browser_window_list' and description 'List all open browser windows (main + popups)' indicate a query operation that retrieves state information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_window_list 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_window_list, this is the rule to start with:

browser_window_list Allowed

browser_window_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_window_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_window_list call is checked against it from then on.

FAQ

Questions about browser_window_list

What does the browser_window_list tool do? +

List all open browser windows (main + popups). It is categorised as a Read tool in the Termux Browser Pilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_window_list? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_window_list: 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.

What risk level is browser_window_list? +

browser_window_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_window_list? +

Yes. Add a rate_limit block to the browser_window_list 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.

How do I block browser_window_list completely? +

Set action: deny in the PolicyLayer policy for browser_window_list. 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.

What MCP server provides browser_window_list? +

browser_window_list 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.

KEEP EXPLORING

More on Termux Browser Pilot, and thousands of servers like it.

This server

All 148 Termux Browser Pilot tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →