获取当前页面加载的所有JavaScript脚本列表
AI agents call js_get_all_scripts to retrieve information from Js Reverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs information gathering only—it lists scripts without modifying, executing, or deleting anything. It is appropriate for JavaScript reverse engineering analysis where understanding what code is loaded is a prerequisite step. The low severity reflects minimal blast radius; an agent misusing this tool can only discover what scripts are present, not execute them or cause harm.
From the tool's definition Tool name is 'js_get_all_scripts' and description states it retrieves ('获取') a list of all JavaScript scripts loaded on the current page. This is purely a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
获取当前页面加载的所有JavaScript脚本列表. 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 js_get_all_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.
js_get_all_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 js_get_all_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 js_get_all_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.
js_get_all_scripts is provided by the Js Reverse MCP server (jenn619/js-reverse-mcp). 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 →