Score likely signature/token/request functions from code files, params, headers, and target URL hints.
AI agents call locate_candidate_functions 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 code analysis and function identification without triggering any code execution, deletion, or data modification. It retrieves and classifies code patterns based on signatures, which is a read-only operation.
From the tool's definition Tool description states it 'Score[s] likely signature/token/request functions from code files, params, headers, and target URL hints' — a querying and analysis operation with no modification or execution.
Attacks that exploit this kind of access
Score likely signature/token/request functions from code files, params, headers, and target URL hints. 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 locate_candidate_functions: 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.
locate_candidate_functions 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 locate_candidate_functions 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 locate_candidate_functions. 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.
locate_candidate_functions 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 →