AI agents call list_scripts to retrieve information from Node Js Debugger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing scripts during a debugging session is a read-only operation that retrieves metadata about loaded scripts. It has no side effects, cannot modify application state, and aligns with the informational debugging operations. While the description is empty, the tool's name and context among other read-only inspection tools provide sufficient confidence that this is a simple enumeration/query operation.
From the tool's definition Tool named 'list_scripts' is listed among debugging tools that provide 'variable inspection', 'stepping', and 'console monitoring'.
Documented attack patterns abuse exactly the kind of access list_scripts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Node Js Debugger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_scripts:
{
"version": "1",
"default": "deny",
"tools": {
"list_scripts": {}
}
}list_scripts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_scripts. It is categorised as a Read tool in the Node Js Debugger MCP MCP Server, which means it retrieves data without modifying state.
Register the Node 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 Node Js Debugger MCP. 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 Node Js Debugger MCP server (scriptedalchemy/devtools-debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Node Js Debugger MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Node Js Debugger MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.