unroute_all

Remove all route interceptors.

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/unroute-all.md

WHAT IT DOES

What unroute_all does on Playwright MCP Server

AI agents invoke unroute_all 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 unroute_all is rated High

Removing all route interceptors changes the runtime behavior of the browser session by disabling network interception/modification rules. This is an operational change to how the browser handles requests, which qualifies as Execute since it affects ongoing browser operations.

From the tool's definition 'Remove all route interceptors' - modifies the active browser automation state by clearing all network route interceptions

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unroute_all 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 unroute_all, this is the rule to start with:

unroute_all Rate-limited

unroute_all 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": {
    "unroute_all": {
      "limits": [
        {
          "counter": "unroute_all_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 unroute_all call is checked against it from then on.

FAQ

Questions about unroute_all

What does the unroute_all tool do? +

Remove all route interceptors. 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 unroute_all? +

Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for unroute_all: 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 unroute_all? +

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

Can I rate-limit unroute_all? +

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

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

unroute_all 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 →