script_test_run · Js Reverse MCP: Risk & Policy

WHAT IT DOES

What script_test_run does on Js Reverse

AI agents invoke script_test_run 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.

WHY IT NEEDS A POLICY

Why script_test_run needs a policy

This tool runs arbitrary generated scripts (JavaScript), which constitutes code execution. In a CTF/web security context, running generated scripts could have wide-ranging effects depending on script content. Severity is high because it executes dynamic code produced by reverse engineering tools, potentially running malicious or unintended logic.

From the tool's definition "测试运行生成的脚本" (test run the generated script) — explicitly executes JavaScript code

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

script_test_run Rate-limited

script_test_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "script_test_run": {
      "limits": [
        {
          "counter": "script_test_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Js Reverse, so you can run agents against it safely.

FAQ

Questions about script_test_run

What does the script_test_run tool do? +

测试运行生成的脚本（仅支持JavaScript，Python需要本地python环境）. 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.

How do I enforce a policy on script_test_run? +

Register the Js Reverse MCP server in PolicyLayer and add a rule for script_test_run: 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.

What risk level is script_test_run? +

script_test_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit script_test_run? +

Yes. Add a rate_limit block to the script_test_run 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.

How do I block script_test_run completely? +

Set action: deny in the PolicyLayer policy for script_test_run. 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.

What MCP server provides script_test_run? +

script_test_run 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.