List Wasm modules captured in the current session.
AI agents call list_wasm_modules 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 enumerates WebAssembly modules from a debugging/analysis session. It performs a query operation that returns information about observed artifacts without creating, modifying, deleting, or executing anything. While it operates in a reverse-engineering context, the tool itself is purely informational and read-only, making it a Read-category risk.
From the tool's definition The tool 'list_wasm_modules' is described as listing (querying) Wasm modules that have been captured. The verb 'list' and the passive framing 'captured in the current session' indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_wasm_modules 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 list_wasm_modules:
{
"version": "1",
"default": "deny",
"tools": {
"list_wasm_modules": {}
}
}list_wasm_modules 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.
List Wasm modules captured in the current session. 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 list_wasm_modules: 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.
list_wasm_modules 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 list_wasm_modules 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 list_wasm_modules. 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.
list_wasm_modules 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.