获取指定脚本的完整源码（自动美化格式化）
AI agents call js_get_script_source 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.
This tool retrieves and formats JavaScript source code from a browser context, enabling analysis and reverse engineering. While classified as Read (no side effects on the target system), the severity is medium rather than low because: (1) extracted source code may contain sensitive logic (encryption keys, authentication tokens, business logic); (2) in a CTF/security testing context, this information could be…
From the tool's definition Tool name 'js_get_script_source' and description indicate retrieval of complete source code from scripts ('获取指定脚本的完整源码' = 'get complete source code of specified script'). This is fundamentally a data retrieval operation with automatic formatting.
Attacks that exploit this kind of access
获取指定脚本的完整源码（自动美化格式化）. 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_script_source: 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_script_source 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_script_source 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_script_source. 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_script_source 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 →