detect_blind_vulnerability

What detect_blind_vulnerability does on Kali Security MCP

AI agents invoke detect_blind_vulnerability to trigger actions in Kali Security MCP. 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 detect_blind_vulnerability is rated High

This tool performs blind injection vulnerability detection by sending crafted payloads to a target and analyzing response differences. This constitutes active probing/exploitation of external systems — an Execute-category action. While it is technically a testing/scanning tool, it actively triggers and manipulates target system behavior (sending injection payloads), which goes beyond passive reading.

From the tool's definition 盲注漏洞检测 - 基于响应差异 (Blind injection vulnerability detection - based on response differences); part of a suite including adaptive_sqli_test, adaptive_web_penetration, and other active exploitation tools

The rule that runs detect_blind_vulnerability safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_blind_vulnerability, this is the rule to start with:

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

Questions about detect_blind_vulnerability