browser_go_back · Scrapeless MCP: Risk & Policy

WHAT IT DOES

What browser_go_back does on Scrapeless

AI agents invoke browser_go_back to trigger actions in Scrapeless. 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 IT NEEDS A POLICY

Why browser_go_back needs a policy

This tool triggers a browser navigation action (equivalent to pressing the Back button), which is an external browser operation. It doesn't read, write, or destroy data on its own, but it executes a browser action that changes the browser state. Severity is low because it only navigates backward in history and cannot cause data loss or significant harm on its own.

From the tool's definition Go back one step in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_go_back Rate-limited

browser_go_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_go_back": {
      "limits": [
        {
          "counter": "browser_go_back_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about browser_go_back

What does the browser_go_back tool do? +

Go back one step in browser history. Restrictions: Only works if a previous page exists in the session history. Valid: After navigating from page A to B, go back to A. Invalid: Attempting to go back on the first page of a session. It is categorised as a Execute tool in the Scrapeless 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_go_back? +

Register the Scrapeless MCP server in PolicyLayer and add a rule for browser_go_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 Scrapeless. Nothing to install.

What risk level is browser_go_back? +

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

Can I rate-limit browser_go_back? +

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

Set action: deny in the PolicyLayer policy for browser_go_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_go_back? +

browser_go_back is provided by the Scrapeless MCP server (scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.