mlsanityData to 14 Oct 2026

Queen-Bee Agents: A BeeSpec-Centered Architecture for Governed Enterprise MCP Orchestration

arXiv 2606.06545 ↗First posted 4 Jun 2026cs.SE cs.AIcited by 0

On the map: LLM agents and tool use → General LLM agent frameworks and benchmarks

Abstract (arXiv)

Enterprise agent systems increasingly need to connect large language models to private tools, internal knowledge, and Model Context Protocol (MCP) interfaces. In this setting, raw task capability is insufficient: organizations also require policy enforcement, tenant-scoped isolation, and execution that remains within explicit operational boundaries. We present Queen-Bee, a governed multi-agent architecture in which a Queen control plane retrieves capabilities, plans task-scoped execution, and compiles a structured BeeSpec that is executed by specialized Bee agents under constrained tool access. We implement a working prototype with tenant-scoped MCP connectors, audit-backed execution-time governance, retrieval-driven weak incubation, and multiple provisioning backends. We evaluate the system on 59 enterprise-style tasks spanning governance-sensitive requests, retrieval-driven provisioning, scoped local execution, and chemistry workflow integration. The retrieval-driven Queen-Bee variant achieves a task success rate of 0.964, zero governance failures, and substantially better scoped execution quality than both a static Queen-Bee baseline and a permissive single-agent baseline. We further show a multi-Bee chemistry workflow with explicit approval gating and a concrete top-3 shortlist grounded in real upstream evidence and screening artifacts. Additional comparisons with hybrid retrieval and LLM-guided provisioning show that richer provisioning backends are viable but do not outperform the lightweight structured retriever on the current small, highly structured capability registry. The results provide prototype-level systems evidence rather than a production deployment study, and suggest that enterprise agent platforms should be evaluated not only by capability, but also by governed provisioning, isolation behavior, scoped execution quality, and artifact-aware workflow coordination.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Placed in General LLM agent frameworks and benchmarks, one of 16 directions in LLM agents and tool use. Builds on 5 of its 9 references that are in the map. First posted on arXiv 4 Jun 2026.

Builds on

5 of 9 references.

Closest ancestors · 1

Same direction, newest first

  1. 2023CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Society31 Mar

Other references · 4

  1. 2022ReAct: Synergizing Reasoning and Acting in Language Modelscited by 8,695
  2. 2023Toolformer: Language Models Can Teach Themselves to Use Toolscited by 4,182
  3. 2023AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversationcited by 1,988
  4. 2023ToolLLM: Facilitating Large Language Models to Master 16000+ Real-world APIscited by 1,947

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026The Orchestration of Multi-Agent Systems: Architectures, Protocols, and Enterprise Adoption
  2. 2026From Tool Orchestration to Code Execution: A Study of MCP Design Choices
  3. 2026Designing Intelligent Enterprise Agents: A Capability-Aligned Multi-Agent Architecture
  4. 2026A Contract-Centered Architecture for Scalable and Manageable Agentic Runtimes
  5. 2026AGL-1: The Enterprise AI Governance Layer as a Control Plane for Trusted Enterprise Intelligence
  6. 2026AgenticCyOps: Securing Multi-Agentic AI Integration in Enterprise Cyber Operations
  7. 2026Governed MCP: Kernel-Level Tool Governance for AI Agents via Logit-Based Safety Primitives
  8. 2026From Tool Connection to Execution Control: Benchmarking Security Invariants in MCP-Style Agent Runtimes