Search in collected script cache with regex pattern.
AI agents call search_in_scripts to retrieve information from JS Reverse Strong MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs pattern matching against previously collected JavaScript code artifacts. It retrieves and filters information from a local cache but does not execute code, modify files, delete data, or trigger external operations. Searching a script cache is a read-only reconnaissance activity with no side effects, appropriate for reverse engineering workflows.
From the tool's definition Tool name 'search_in_scripts' combined with description 'Search in collected script cache with regex pattern' indicates a query operation over cached data.
Documented attack patterns abuse exactly the kind of access search_in_scripts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_in_scripts:
{
"version": "1",
"default": "deny",
"tools": {
"search_in_scripts": {}
}
}search_in_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.
Search in collected script cache with regex pattern. It is categorised as a Read tool in the JS Reverse Strong MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse Strong MCP server in PolicyLayer and add a rule for search_in_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 Strong MCP. Nothing to install.
search_in_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 search_in_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 search_in_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.
search_in_scripts is provided by the JS Reverse Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JS Reverse Strong MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.