select_page · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What select_page does on JS Reverse MCP

AI agents invoke select_page to trigger actions in JS Reverse 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 IT NEEDS A POLICY

Why select_page needs a policy

This tool sets the active browser page context, which is an action that affects the state of browser automation. While it doesn't directly execute code or modify data, it controls which page future Execute-level operations target, making it an Execute-category action in the context of a browser debugging/automation server. Misuse could redirect subsequent operations to unintended pages.

From the tool's definition Select a page as a context for future tool calls — sets the active browser page/tab context for subsequent browser automation actions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_page Rate-limited

select_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_page": {
      "limits": [
        {
          "counter": "select_page_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches JS Reverse MCP, so you can run agents against it safely.

FAQ

Questions about select_page

What does the select_page tool do? +

Select a page as a context for future tool calls. It is categorised as a Execute tool in the JS Reverse 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 select_page? +

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

What risk level is select_page? +

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

Can I rate-limit select_page? +

Yes. Add a rate_limit block to the select_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.

How do I block select_page completely? +

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

What MCP server provides select_page? +

select_page is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.