list_pages
Get a list of pages open in the browser.
This record as markdown: /tools/1600822305-js-reverse-mcp/list-pages.md
What list_pages does on Js Reverse
AI agents call list_pages to retrieve information from Js Reverse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_pages is rated Low
This tool retrieves information about open browser pages without side effects. It is purely informational and does not modify, execute, delete, or move any data. The low severity reflects minimal blast radius — an agent misusing this can only enumerate pages, not interact with or modify them.
From the tool's definition Tool is named 'list_pages' and described as 'Get a list of pages open in the browser' — a direct retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs list_pages 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 list_pages, this is the rule to start with:
list_pages is read-only, so it stays allowed. 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 list_pages call is checked against it from then on.
Questions about list_pages
Get a list of pages open in the browser. It is categorised as a Read tool in the Js Reverse MCP Server, which means it retrieves data without modifying state.
Register the Js Reverse MCP server in PolicyLayer and add a rule for list_pages: 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.
list_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_pages 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 list_pages. 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.
list_pages 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.
This server
Across the catalogue