AI agents call detect_crypto_algorithm to retrieve information from Js Reverse Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs passive detection and analysis of existing code patterns. It retrieves information about what cryptographic algorithms are present in JavaScript code. No code execution, data modification, deletion, or financial operations occur. The tool sits alongside execute_js_safely and bypass_challenge on the server, but this specific tool is purely analytical.
From the tool's definition Tool name 'detect_crypto_algorithm' and description '检测 JS 代码中使用的加密算法' (detect encryption algorithms used in JS code) indicate static analysis that identifies cryptographic methods without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access detect_crypto_algorithm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Js Reverse Analyzer, and nothing reaches the server without passing your rules. This is the rule we recommend for detect_crypto_algorithm:
{
"version": "1",
"default": "deny",
"tools": {
"detect_crypto_algorithm": {}
}
}detect_crypto_algorithm 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.
检测 JS 代码中使用的加密算法. It is categorised as a Read tool in the Js Reverse Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Js Reverse Analyzer MCP server in PolicyLayer and add a rule for detect_crypto_algorithm: 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 Analyzer. Nothing to install.
detect_crypto_algorithm 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 detect_crypto_algorithm 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 detect_crypto_algorithm. 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.
detect_crypto_algorithm is provided by the Js Reverse Analyzer MCP server (sjhhh024-cmyk/spider-js-mcp-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Js Reverse Analyzer, 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.
13 Js Reverse Analyzer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.