generate_poc_from_current_session

What generate_poc_from_current_session does on Kali Security MCP

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

Generating a Proof of Concept (PoC) from an active session in a penetration testing framework involves synthesizing and executing exploit logic or attack scripts. This is an Execute-category action because it produces runnable exploit code/scripts and may trigger external operations. The blast radius is high because the generated PoC can be used to exploit real vulnerabilities in target systems.

From the tool's definition '生成PoC' (generate PoC) from current active session - PoC (Proof of Concept) generation involves executing or scripting exploit code derived from the current penetration testing session

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

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

Questions about generate_poc_from_current_session