追踪指定函数的调用链(谁调用了它,它又调用了谁)
AI agents invoke js_trace_call_chain to trigger actions in Js Reverse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool traces function call chains dynamically within a browser context (part of a browser-based JS reverse engineering server). It executes runtime instrumentation to monitor who calls a function and what it calls, which involves active execution of tracing logic in the browser. It is not a simple passive read; it hooks into running code, placing it in the Execute category.
From the tool's definition 追踪指定函数的调用链(谁调用了它,它又调用了谁) — traces function call chains in a live browser environment, implying dynamic instrumentation/execution of browser JS analysis
Attacks that exploit this kind of access
追踪指定函数的调用链(谁调用了它,它又调用了谁). It is categorised as a Execute tool in the Js Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Js Reverse MCP server in PolicyLayer and add a rule for js_trace_call_chain: 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.
js_trace_call_chain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the js_trace_call_chain 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 js_trace_call_chain. 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.
js_trace_call_chain 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 →