switch_page
A execute tool on the Playwright MCP server.
This record as markdown: /tools/alexrwilliam-playwright-mcp-server/switch-page.md
What switch_page does on Playwright MCP Server
AI agents invoke switch_page 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.
Why switch_page is rated High
This tool exists on a Playwright MCP server that performs browser automation (webpage interaction, DOM manipulation). 'switch_page' likely switches the active browser page/tab context, which is an Execute-level browser action. However, the description is empty, so confidence is reduced.
From the tool's definition Tool name 'switch_page' on a Playwright browser automation server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs switch_page 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 switch_page, this is the rule to start with:
switch_page 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 MCP Server, apply this rule, and every switch_page call is checked against it from then on.
Questions about switch_page
switch_page 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.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for switch_page: 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.
switch_page 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 switch_page 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 switch_page. 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.
switch_page 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.
More on Playwright MCP Server, and thousands of servers like it.
Across the catalogue