chrome_go_back_or_forward · Chrome MCP Server MCP

WHAT IT DOES

What chrome_go_back_or_forward does on Chrome MCP Server

AI agents invoke chrome_go_back_or_forward to trigger actions in Chrome 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 chrome_go_back_or_forward needs a policy

This tool controls browser navigation (back/forward), which triggers external operations in the browser. It's not purely reading data, nor writing/creating content — it executes a browser action that changes the browser's state and may load different pages, potentially exposing new content or triggering page-side effects. Description is minimal, lowering confidence slightly.

From the tool's definition 'Browser navigation control' — triggers browser navigation actions (go back or forward), which are external browser operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_go_back_or_forward Rate-limited

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

FAQ

Questions about chrome_go_back_or_forward

What does the chrome_go_back_or_forward tool do? +

Browser navigation control. It is categorised as a Execute tool in the Chrome 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 chrome_go_back_or_forward? +

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

What risk level is chrome_go_back_or_forward? +

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

Can I rate-limit chrome_go_back_or_forward? +

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

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

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