list_scripts

Lists all JavaScript scripts loaded in the current page. Returns script ID, URL, and source map information. Use this to find scripts before setting breakpoints or searching.

SERVERJs Reverse SOURCE1600822305/js-reverse-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1600822305-js-reverse-mcp/list-scripts.md

WHAT IT DOES

What list_scripts does on Js Reverse

AI agents call list_scripts 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.

RISK

Why list_scripts is rated Low

This tool retrieves and queries information about JavaScript scripts in the browser's current page context. It performs no modifications, deletions, code execution, or financial operations. It is purely informational, supporting the debugging and reverse engineering workflow by enumerating available scripts.

From the tool's definition Tool description states it 'Lists all JavaScript scripts loaded in the current page' and returns 'script ID, URL, and source map information'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_scripts Allowed

list_scripts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_scripts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every list_scripts call is checked against it from then on.

FAQ

Questions about list_scripts

What does the list_scripts tool do? +

Lists all JavaScript scripts loaded in the current page. Returns script ID, URL, and source map information. Use this to find scripts before setting breakpoints or searching. It is categorised as a Read tool in the Js Reverse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_scripts? +

Register the Js Reverse MCP server in PolicyLayer and add a rule for list_scripts: 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.

What risk level is list_scripts? +

list_scripts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_scripts? +

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

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

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

KEEP EXPLORING

More on Js Reverse, and thousands of servers like it.

This server

All 93 Js Reverse tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →