Collect JavaScript code from a page with smart modes (summary/priority/incremental/full).
AI agents call collect_code 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 retrieves and observes JavaScript code from a running page—a read operation with no side effects on the target system. However, severity is elevated to 'medium' rather than 'low' because collected code may contain sensitive logic, API keys, authentication tokens, or proprietary algorithms. An agent could exfiltrate intellectual property or credentials.
From the tool's definition Tool name 'collect_code' and description 'Collect JavaScript code from a page' indicates retrieval of code artifacts. The phrase 'smart modes (summary/priority/incremental/full)' indicates configurable querying/sampling without modification.
Documented attack patterns abuse exactly the kind of access collect_code 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 collect_code:
{
"version": "1",
"default": "deny",
"tools": {
"collect_code": {}
}
} collect_code 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.
Collect JavaScript code from a page with smart modes (summary/priority/incremental/full). 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 collect_code: 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.
collect_code 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 collect_code 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 collect_code. 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.
collect_code 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.