go_forward · Chrome Profile MCP Server MCP: Risk & Policy

WHAT IT DOES

What go_forward does on Chrome Profile MCP Server

AI agents invoke go_forward to trigger actions in Chrome Profile MCP Server. 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 go_forward needs a policy

Navigating forward in browser history triggers page loads and executes browser actions that can have side effects depending on what page is loaded. This is a browser control action that affects the state of an external application (Chrome), classifying it as Execute rather than Read.

From the tool's definition Go forward in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

go_forward Rate-limited

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": {
    "go_forward": {
      "limits": [
        {
          "counter": "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 Chrome Profile MCP Server, so you can run agents against it safely.

FAQ

Questions about go_forward

What does the go_forward tool do? +

Go forward in browser history. It is categorised as a Execute tool in the Chrome Profile MCP Server 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_forward? +

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

What risk level is go_forward? +

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

Can I rate-limit go_forward? +

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

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

go_forward is provided by the Chrome Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.