browser_window_close

Close the current browser window (popup).

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What browser_window_close does on Termux Browser Pilot

AI agents call browser_window_close to permanently remove resources in Termux Browser Pilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why browser_window_close is rated Critical

Closing a browser window is an irreversible action — once closed, any unsaved state, session data, or form inputs in that window are lost and cannot be recovered. This matches the Destructive category (irreversibly destroys in-memory/session state). Severity is medium because the blast radius is limited to the current window's state rather than persistent data or finances.

From the tool's definition Close the current browser window (popup)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_window_close Hidden

browser_window_close is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "browser_window_close"
  ]
}

RESTRICT 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_close call is checked against it from then on.

FAQ

Questions about browser_window_close

What does the browser_window_close tool do? +

Close the current browser window (popup). It is categorised as a Destructive tool in the Termux Browser Pilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on browser_window_close? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_window_close: 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_close? +

browser_window_close is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit browser_window_close? +

Yes. Add a rate_limit block to the browser_window_close 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_close completely? +

Set action: deny in the PolicyLayer policy for browser_window_close. 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_close? +

browser_window_close 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →