go_back

A execute tool on the Playwright MCP server.

SERVERPlaywright MCP Server SOURCEalexrwilliam/playwright-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexrwilliam-playwright-mcp-server/go-back.md

WHAT IT DOES

What go_back does on Playwright MCP Server

AI agents invoke go_back to trigger actions in Playwright 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.

RISK

Why go_back is rated High

In the context of a Playwright browser automation server, 'go_back' almost certainly triggers the browser's back navigation action (equivalent to clicking the browser back button), which is an external operation that changes browser state. This is an Execute-level action as it triggers a browser operation.

From the tool's definition Tool name 'go_back' on a Playwright browser automation server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs go_back safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For go_back, this is the rule to start with:

go_back Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Playwright MCP Server, apply this rule, and every go_back call is checked against it from then on.

FAQ

Questions about go_back

What does the go_back tool do? +

go_back is a execute tool on the Playwright MCP Server MCP server. It is categorised as a Execute tool in the Playwright 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_back? +

Register the Playwright MCP Server 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 Playwright MCP Server. 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 Playwright MCP Server MCP server (alexrwilliam/playwright-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Playwright MCP Server, and thousands of servers like it.

This server

All 67 Playwright MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →