This record as markdown: /tools/1600822305-js-reverse-mcp/new-page.md
What new_page does on Js Reverse
AI agents invoke new_page to trigger actions in Js Reverse. 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 new_page is rated High
Creating a new browser page is a control operation with side effects beyond simple data retrieval. While not destructive or financial, it executes browser operations and can trigger code execution on the created page. The tool enables browser automation whose consequences depend on what runs afterward.
From the tool's definition The tool 'Creates a new page' on a Chrome DevTools Protocol server that 'enable[s] AI coding assistants to control browsers' represents execution of browser control operations.
Attacks that exploit this kind of access
The rule that runs new_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For new_page, this is the rule to start with:
new_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 Js Reverse, apply this rule, and every new_page call is checked against it from then on.
Questions about new_page
Creates a new page. It is categorised as a Execute tool in the Js Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Js Reverse MCP server in PolicyLayer and add a rule for new_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 Js Reverse. Nothing to install.
new_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 new_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 new_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.
new_page is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
Across the catalogue