获取加密函数及其所有依赖的完整上下文（函数本身+引用的变量/函数）
AI agents call js_get_encryption_context to retrieve information from Js Reverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing JavaScript code and variables within a browser context for reverse-engineering purposes. It is fundamentally a Read operation: it queries the state of running JavaScript without executing new code or modifying the page.
From the tool's definition Tool name 'js_get_encryption_context' and description '获取加密函数及其所有依赖的完整上下文（函数本身+引用的变量/函数）' (get complete context of encryption functions and all their dependencies) indicate data retrieval from browser JavaScript execution context.
Attacks that exploit this kind of access
获取加密函数及其所有依赖的完整上下文（函数本身+引用的变量/函数）. 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 js_get_encryption_context: 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.
js_get_encryption_context 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 js_get_encryption_context 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 js_get_encryption_context. 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.
js_get_encryption_context is provided by the Js Reverse MCP server (jenn619/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
js_get_encryption_context is one line of Js Reverse's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →