browser_navigate_back

A execute tool on the Playwright MCP server.

SERVERPlaywright MCP SOURCEalialobidm/playwright-mcp
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/alialobidm-playwright-mcp/browser-navigate-back.md

What browser_navigate_back does on Playwright MCP

AI agents invoke browser_navigate_back to trigger actions in Playwright MCP. 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 browser_navigate_back is rated High

This tool executes a browser command (navigate back) rather than merely reading data. While navigation itself is not destructive or financial, it is an Execute-category action because it triggers an external operation with side effects—changing the current page and potentially re-executing scripts or modifying client-side state.

From the tool's definition Tool name 'browser_navigate_back' indicates it triggers browser back navigation, an external operation that modifies browser state.

Questions about browser_navigate_back

What does the browser_navigate_back tool do? +

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

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

What risk level is browser_navigate_back? +

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

Can I rate-limit browser_navigate_back? +

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

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

browser_navigate_back is provided by the Playwright MCP server (alialobidm/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Playwright, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Playwright's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.