browser_back

Navigate back in browser history. Returns new URL and title.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What browser_back does on Termux Browser Pilot

AI agents invoke browser_back 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.

RISK

Why browser_back is rated High

This tool triggers a browser navigation action (going back in history), which is an external browser operation with side effects. While it seems benign, it changes the browser state and could affect ongoing interactions or forms. It fits Execute as it performs a browser action rather than merely reading data.

From the tool's definition Navigate back in browser history. Returns new URL and title.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_back Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT 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_back call is checked against it from then on.

FAQ

Questions about browser_back

What does the browser_back tool do? +

Navigate back in browser history. Returns new URL and title. 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.

How do I enforce a policy on browser_back? +

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

browser_back is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_back? +

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

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

browser_back 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 → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →