Lists all scripts loaded in the debugging session.
AI agents call list_scripts to retrieve information from MCP JS Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and enumerates scripts without modifying, deleting, or executing anything. However, severity is elevated to 'medium' rather than 'low' because the information retrieved (loaded scripts, including their source code accessible via sibling tools like get_script_source) could expose sensitive application logic, environment-specific code paths, or internal implementation details to an AI agent, making…
From the tool's definition Tool name 'list_scripts' and description 'Lists all scripts loaded in the debugging session' indicate a retrieval operation with no side effects. This is a query operation that retrieves information about loaded scripts.
Attacks that exploit this kind of access
Lists all scripts loaded in the debugging session. It is categorised as a Read tool in the MCP JS Debugger MCP Server, which means it retrieves data without modifying state.
Register the MCP JS Debugger 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 MCP JS Debugger. Nothing to install.
list_scripts 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_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.
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.
list_scripts is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →