ai_reconnaissance_workflow

What ai_reconnaissance_workflow does on Nyxstrike

AI agents invoke ai_reconnaissance_workflow to trigger actions in Nyxstrike. 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 ai_reconnaissance_workflow is rated High

Reconnaissance workflows in offensive security contexts actively probe, scan, and enumerate targets (external systems, networks, hosts). Given the server is an 'AI Powered penetration testing Platform for offensive security research' and sibling tools include active attack tools (aireplay_ng, aircrack_ng, payload generation), this tool almost certainly executes active network/system reconnaissance against targets.

From the tool's definition Tool name 'ai_reconnaissance_workflow' on a penetration testing platform with sibling tools like 'advanced_payload_generation', 'ai_generate_attack_suite', 'aireplay_ng', and 'aircrack_ng' — all offensive security tools.

The rule that runs ai_reconnaissance_workflow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai_reconnaissance_workflow, this is the rule to start with:

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

Questions about ai_reconnaissance_workflow