browser_forward · Ruflo MCP: Risk & Policy

WHAT IT DOES

What browser_forward does on Ruflo

AI agents invoke browser_forward to trigger actions in Ruflo. 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_forward needs a policy

This tool executes a browser action (navigating forward in history) within a real browser automation context. It triggers external operations in a live browser session, including potential interaction with JS-heavy SPAs and login flows. While a single navigation step has limited blast radius on its own, it operates within a session that could include authenticated state and sensitive data, warranting medium severity.

From the tool's definition Navigate forward in browser history... you need real browser automation — JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_forward Rate-limited

browser_forward 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_forward": {
      "limits": [
        {
          "counter": "browser_forward_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 Ruflo, so you can run agents against it safely.

FAQ

Questions about browser_forward

What does the browser_forward tool do? +

Navigate forward in browser history Use when native WebFetch is wrong because you need real browser automation — JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions, AIDefence PII gating before content reaches Claude. For static HTML pages, native WebFetch is faster and free. It is categorised as a Execute tool in the Ruflo 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_forward? +

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

What risk level is browser_forward? +

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

Can I rate-limit browser_forward? +

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

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

browser_forward is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.