get_script_source
Gets the source code of a JavaScript script by its script ID. Supports line range (for normal files) or character offset (for minified single-line files). Use list_scripts first to find the script ID.
This record as markdown: /tools/1600822305-js-reverse-mcp/get-script-source.md
What get_script_source does on Js Reverse
AI agents call get_script_source 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.
Why get_script_source is rated Low
This tool performs a query/retrieval operation with no side effects. It accesses existing script source code without creating, modifying, deleting, or executing anything. The blast radius is minimal since reading JavaScript source code in a debugging context poses negligible risk compared to tools that modify browser state or execute arbitrary code.
From the tool's definition Tool retrieves source code of JavaScript scripts: 'Gets the source code of a JavaScript script by its script ID'. No modification, deletion, or execution is described—only retrieval with optional filtering by line range or character offset.
Attacks that exploit this kind of access
The rule that runs get_script_source 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 get_script_source, this is the rule to start with:
get_script_source is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every get_script_source call is checked against it from then on.
Questions about get_script_source
Gets the source code of a JavaScript script by its script ID. Supports line range (for normal files) or character offset (for minified single-line files). Use list_scripts first to find the script ID. 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 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.
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 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 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.
get_script_source 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.
More on Js Reverse, and thousands of servers like it.
This server
Across the catalogue