browser_back · Browser MCP: Risk & Policy

WHAT IT DOES

What browser_back does on BrowserMCP

AI agents use browser_back to create or update resources in BrowserMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BrowserMCP environment.

WHY IT NEEDS A POLICY

Why browser_back needs a policy

An AI agent can call browser_back faster than any human can review — one bad instruction and it creates or modifies resources in BrowserMCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_back Rate-limited

browser_back stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BrowserMCP, so you can run agents against it safely.

FAQ

Questions about browser_back

What does the browser_back tool do? +

Navigate back in browser history. It is categorised as a Write tool in the BrowserMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_back? +

Register the Browser 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 BrowserMCP. Nothing to install.

What risk level is browser_back? +

browser_back is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 Browser MCP server (smotree/browsermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.