Detect cryptographic algorithms/libraries from JavaScript source.
AI agents call detect_crypto to retrieve information from JS Reverse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs source code analysis to identify cryptographic implementations. It retrieves and queries information about algorithms present in JavaScript without side effects, state changes, or execution of arbitrary code. The analysis is passive and informational, making it a Read operation with low severity since it merely detects what exists rather than executing, modifying, or removing data.
From the tool's definition Tool name 'detect_crypto' and description 'Detect cryptographic algorithms/libraries from JavaScript source' indicate static analysis and detection of existing cryptographic patterns in code without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Detect cryptographic algorithms/libraries from JavaScript source. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse MCP server in PolicyLayer and add a rule for detect_crypto: 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 MCP. Nothing to install.
detect_crypto 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 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. 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 is provided by the JS Reverse MCP server (noone-hub/jsreverser-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 →