browser_unroute
A execute tool on the Playwright MCP server.
This record as markdown: /tools/hanato238-playwright-mcp/browser-unroute.md
What browser_unroute does on Playwright
AI agents invoke browser_unroute to trigger actions in Playwright. 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_unroute is rated High
Based on the tool name, this appears to remove a network route/intercept previously set up in the browser (unregistering a request handler). This is an Execute-class operation as it modifies browser automation state. However, the description is empty so confidence is low. It's unlikely to be Destructive or Financial, and it's more than a passive Read since it changes browser routing configuration.
From the tool's definition Tool name 'browser_unroute' and server description mentions browser automation. Description is empty, lowering confidence.
Attacks that exploit this kind of access
The rule that runs browser_unroute safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_unroute, this is the rule to start with:
browser_unroute 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Playwright, apply this rule, and every browser_unroute call is checked against it from then on.
Questions about browser_unroute
browser_unroute is a execute tool on the Playwright MCP server. It is categorised as a Execute tool in the Playwright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_unroute: 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. Nothing to install.
browser_unroute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_unroute 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.
Set action: deny in the PolicyLayer policy for browser_unroute. 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.
browser_unroute is provided by the Playwright MCP server (hanato238/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.
Across the catalogue