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.
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.
Documented attack patterns abuse exactly the kind of access trigger_next_attack_phase 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 trigger_next_attack_phase:
{
"version": "1",
"default": "deny",
"tools": {
"trigger_next_attack_phase": {
"limits": [
{
"counter": "trigger_next_attack_phase_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}trigger_next_attack_phase 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 trigger_next_attack_phase: 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.
trigger_next_attack_phase 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 trigger_next_attack_phase 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 trigger_next_attack_phase. 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.
trigger_next_attack_phase 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.