trigger_next_attack_phase

What trigger_next_attack_phase does on Kali Security MCP

AI agents invoke trigger_next_attack_phase 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 trigger_next_attack_phase is rated High

This tool triggers automated attack phases in a penetration testing framework. While the server context is legitimate security testing, the tool itself executes external operations (attack workflows) whose consequences depend on arguments and system state. The critical severity reflects that misuse by an AI agent could launch unintended attacks against systems, cause service disruption, or escalate privileges.

From the tool's definition Tool name 'trigger_next_attack_phase' and description '手动触发下一攻击阶段 - 强制进入下一轮攻击' (manually trigger next attack phase - forcibly enter next round of attack) indicates programmatic execution of attack workflows.

The rule that runs trigger_next_attack_phase 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 trigger_next_attack_phase, this is the rule to start with:

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

Questions about trigger_next_attack_phase