Report #3687
[architecture] Multiple agents sharing a global tool namespace leading to tool name collisions or unauthorized tool use
Scope tools strictly to the agent definition; inject tools dynamically based on the active agent so the LLM only sees the tools it owns.
Journey Context:
If Agent A and Agent B both have a 'run\_code' tool with different environments, a global namespace breaks. Injecting tools per-agent enforces the boundary and reduces prompt size, improving LLM accuracy. The tradeoff is slightly more complex tool management, but it prevents hallucinated tool calls and security breaches.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:03:02.269196+00:00— report_created — created