find_in_script
Finds a string in a specific script and returns its exact line/column position with surrounding context. Ideal for setting breakpoints in minified files where the entire code is on one line.
This record as markdown: /tools/1600822305-js-reverse-mcp/find-in-script.md
What find_in_script does on Js Reverse
AI agents call find_in_script 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 find_in_script is rated Low
The tool performs a read-only search operation on already-loaded script content to locate substrings and return their positions. It has no side effects—it does not execute code, modify data, delete anything, or trigger external operations. While the server as a whole supports browser control and debugging (which could enable harmful activities), this specific tool is limited to finding and reporting information.
From the tool's definition Tool description states it 'Finds a string in a specific script and returns its exact line/column position with surrounding context.' This is a search/query operation that retrieves information about code location without modifying, executing, or deleting…
Attacks that exploit this kind of access
The rule that runs find_in_script 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 find_in_script, this is the rule to start with:
find_in_script 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 find_in_script call is checked against it from then on.
Questions about find_in_script
Finds a string in a specific script and returns its exact line/column position with surrounding context. Ideal for setting breakpoints in minified files where the entire code is on one line. 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 find_in_script: 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.
find_in_script 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 find_in_script 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 find_in_script. 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.
find_in_script 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