go_back

THE RISK

High Risk

This tool triggers a browser navigation action (going back in history), which is an external browser operation with side effects depending on the current browser state. It falls under Execute as it controls browser behavior rather than simply reading data or writing/deleting it.

From the tool's definition Navigate backward in browser history (Back button). Returns new page URL.

Documented attack patterns abuse exactly the kind of access go_back gives an agent:

HOW TO CONTROL GO_BACK

PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for go_back:

policy.json

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

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.

Create a free account and register Camofox — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Camofox tools

Destructive delete_download Delete a downloaded file from disk and registry Destructive delete_profile Delete a saved browser profile from disk. Removes the profile Execute camofox_evaluate_js Execute JavaScript in the browser page context. Runs in isolated scope (invisible to page Execute camofox_hover Hover over an element to trigger tooltips, dropdown menus, or hover states. Use ref from s Execute camofox_wait_for Wait for page to be fully ready (DOM loaded, network idle, framework hydration complete). Execute camofox_wait_for_selector Wait for a CSS selector to appear in the live DOM. Use for SPA hydration and async content Execute camofox_wait_for_text Wait for specific text to appear on the page. Useful for waiting for search results, form Execute navigate Navigate a tab to a URL. Waits for page load. Use create_tab first, then navigate. Returns

All 47 Camofox tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Camofox → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the go_back tool do? +

Navigate backward in browser history (Back button). Returns new page URL. It is categorised as a Execute tool in the Camofox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on go_back? +

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

What risk level is go_back? +

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

Can I rate-limit go_back? +

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

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

go_back is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Camofox tool call.

Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN CAMOFOX →

Free to start. No card required.

47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT GO_BACK ON CAMOFOX DOES

// THE RISK

// HOW TO CONTROL GO_BACK

// EXPLORE