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.
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
Documented attack patterns abuse exactly the kind of access detect_blind_vulnerability gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for detect_blind_vulnerability:
{
"version": "1",
"default": "deny",
"tools": {
"detect_blind_vulnerability": {
"limits": [
{
"counter": "detect_blind_vulnerability_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}detect_blind_vulnerability 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.
Free to start. No card required.
盲注漏洞检测 - 基于响应差异. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security MCP server in PolicyLayer and add a rule for detect_blind_vulnerability: 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 Security MCP. Nothing to install.
detect_blind_vulnerability 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 detect_blind_vulnerability 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 detect_blind_vulnerability. 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.
detect_blind_vulnerability is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.