playwright_go_back · Playwright MCP Server for Security MCP

WHAT IT DOES

What playwright_go_back does on Playwright MCP Server for Security

AI agents invoke playwright_go_back to trigger actions in Playwright MCP Server for Security. 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 playwright_go_back needs a policy

This tool triggers a browser navigation action (going back in history), which is an external operation that changes the browser state. It is not a simple read operation—it causes side effects by altering the current page and browser history position, qualifying it as Execute.

From the tool's definition Navigate back in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

playwright_go_back Rate-limited

playwright_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": {
    "playwright_go_back": {
      "limits": [
        {
          "counter": "playwright_go_back_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 Playwright MCP Server for Security, so you can run agents against it safely.

FAQ

Questions about playwright_go_back

What does the playwright_go_back tool do? +

Navigate back in browser history. It is categorised as a Execute tool in the Playwright MCP Server for Security MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on playwright_go_back? +

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

What risk level is playwright_go_back? +

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

Can I rate-limit playwright_go_back? +

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

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

playwright_go_back is provided by the Playwright MCP Server for Security MCP server (o0x1024/mcp-playwright-security). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.