Trace a captured network request to initiator stack frames and optional static code candidates.
AI agents call trace_request_to_code 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.
While this tool operates within a browser debugging context (which inherently involves inspection and tracing capabilities), the primary function described is analytical—it traces and maps network requests to their initiator code without performing destructive, write, or financial operations.
From the tool's definition Tool traces/traces network requests to stack frames and code candidates; enables analysis and inspection of captured network data and code flow without modifying, deleting, or executing arbitrary code.
Attacks that exploit this kind of access
Trace a captured network request to initiator stack frames and optional static code candidates. 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 trace_request_to_code: 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.
trace_request_to_code 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 trace_request_to_code 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 trace_request_to_code. 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.
trace_request_to_code 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 →