js_scan_analyze · Kali MCP: Risk & Policy

WHAT IT DOES

What js_scan_analyze does on Kali

AI agents invoke js_scan_analyze to trigger actions in Kali. 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 js_scan_analyze needs a policy

The tool executes an external JavaScript analysis/scanning tool (JS-Scan) on a target. Running active analysis tools against web targets constitutes code/tool execution with potentially significant side effects depending on the target. On a pentesting platform, this could be used offensively to enumerate JavaScript endpoints, secrets, or vulnerabilities in target applications.

From the tool's definition 'Execute JS-Scan JavaScript analysis tool' — explicitly runs an external tool; part of a Kali Linux penetration testing server supporting 'network scanning, web scanning, password attacks'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

js_scan_analyze Rate-limited

js_scan_analyze 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": {
    "js_scan_analyze": {
      "limits": [
        {
          "counter": "js_scan_analyze_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 Kali, so you can run agents against it safely.

FAQ

Questions about js_scan_analyze

What does the js_scan_analyze tool do? +

Execute JS-Scan JavaScript analysis tool. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on js_scan_analyze? +

Register the Kali MCP server in PolicyLayer and add a rule for js_scan_analyze: 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 Kali. Nothing to install.

What risk level is js_scan_analyze? +

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

Can I rate-limit js_scan_analyze? +

Yes. Add a rate_limit block to the js_scan_analyze 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 js_scan_analyze completely? +

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

js_scan_analyze is provided by the Kali MCP server (pentestt00ls/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.