2026-10-29 15:08 UTC
----------------
🛠️ Tool
===================
Vulnerator AI: Hermes agent drives an OODA pentest loop against a Kali container
The project pairs a language-model agent with a live Kali Linux environment and lets the agent run offensive tooling directly against a target. The driving brain is Hermes, the agent framework from Nous Research, and the runtime is a Kali container governed by an MCP server. The agent observes tool output, orients on it, decides the next action, and acts by launching tools straight through the Kali MCP. Nothing sits between the decision-maker and the tooling, and there are no human approval gates in the loop.
Key characteristics
• An OODA (Observe-Orient-Decide-Act) loop structures the agent's decisions instead of a flat tool-calling chain
• Hermes talks directly to the Kali MCP server, with no orchestration layer in between
• The design is deliberately minimal: no core service, no REST API, no UI, no approval gates
• Four containers make up the deployment: the agent, two tool MCP servers, and the MCP front door
• A demo video shows the loop in action
Technical implementation
Docker handles the whole deployment. Configuration goes through a .env file: set an OPENROUTER_API_KEY and generate two tokens with openssl rand -hex 32. The repository ships a security pipeline with CodeQL scanning and PR quality checks. One caveat on sourcing: the published README cuts off mid-sentence in the architecture section, so the exact roles of the two tool MCP servers and the networking between containers are not documented in the material available. What is present confirms the four-container layout and the direct agent-to-Kali path.
Use cases
• Automated recon-to-exploitation workflows in authorized lab environments
• Studying how agentic models handle offensive decisions end to end, since Hermes owns tool selection
• A minimal reference point for anyone building an MCP-governed tool runtime, useful when comparing against heavier frameworks
Limitations
• Haven't tested this personally; the source is the project's own README, not a validated engagement report
• No approval gates means the agent acts on its own decisions. That is the point for lab work and a liability anywhere production infrastructure is reachable
• The truncated architecture section makes container roles and networking details hard to confirm
• Scoping and authorization discipline fall entirely on the operator
References
Demo video in the repository, the Hermes agent project from Nous Research, and the Kali Linux tooling runtime. Releases are versioned on GitHub.
🔹 tool #MCP #AIAgents #pentest #OODA
🔗 Source: https://github.com/irraz/vulnerator-ai
Replies (0)
No replies.