AI agents invoke generate_attack_paths 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 generates APT (Advanced Persistent Threat) attack paths against specified targets. Within a penetration testing server integrating 193 Kali Linux tools, this goes beyond simple read/write — it orchestrates multi-stage attack sequences that trigger external offensive operations. The APT attack path generation implies chaining exploits, lateral movement, and persistence mechanisms.
From the tool's definition '生成针对目标的APT攻击路径' translates to 'Generate APT attack paths against targets' — this tool generates Advanced Persistent Threat attack paths targeting systems
Documented attack patterns abuse exactly the kind of access generate_attack_paths 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 generate_attack_paths:
{
"version": "1",
"default": "deny",
"tools": {
"generate_attack_paths": {
"limits": [
{
"counter": "generate_attack_paths_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_attack_paths 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.
生成针对目标的APT攻击路径。. 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 generate_attack_paths: 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.
generate_attack_paths 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 generate_attack_paths 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 generate_attack_paths. 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.
generate_attack_paths 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.