自动扫描页面所有JS代码，检测使用的加密算法和库（支持AES/DES/RSA/MD5/SHA/SM2/SM4/Base64）
AI agents call crypto_auto_detect 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 is a passive analysis tool that retrieves and analyzes information about encryption implementations on a webpage. It has no side effects, does not execute arbitrary code, does not modify data, and does not delete anything. It is purely informational/investigative in nature, consistent with reverse engineering workflows.
From the tool's definition Tool performs automatic scanning and detection of encryption algorithms and libraries used in page JavaScript code. Description indicates 'scan', 'detect', and 'analyze' operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
自动扫描页面所有JS代码，检测使用的加密算法和库（支持AES/DES/RSA/MD5/SHA/SM2/SM4/Base64）. 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 crypto_auto_detect: 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.
crypto_auto_detect 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 crypto_auto_detect 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 crypto_auto_detect. 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.
crypto_auto_detect 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →