browser_go_forward · Abrasio MCP: Risk & Policy

WHAT IT DOES

What browser_go_forward does on Abrasio

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

This tool triggers a browser navigation action (moving forward in history), which is an external operation with effects that depend on the current browser state. It controls a real web browser, making it an Execute-category action. Misuse could navigate to unintended pages, but the blast radius is moderate.

From the tool's definition Go forward to the next page in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_go_forward Rate-limited

browser_go_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_go_forward": {
      "limits": [
        {
          "counter": "browser_go_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 Abrasio, so you can run agents against it safely.

FAQ

Questions about browser_go_forward

What does the browser_go_forward tool do? +

Go forward to the next page in browser history. It is categorised as a Execute tool in the Abrasio 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_forward? +

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

What risk level is browser_go_forward? +

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

Can I rate-limit browser_go_forward? +

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

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

browser_go_forward is provided by the Abrasio MCP server (scrape-technology/abrasio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_go_forward is one line of Abrasio's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →