Repository navigation
An independent Tool Runtime for dynamic and secure Tool management in Spring AI #7074
GreenDay1991
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I encountered a related challenge while building an enterprise application with Spring AI.
In a team-based enterprise environment, tools are not always static code-level capabilities. They may need to be discovered, registered, governed, secured, and reused dynamically as business requirements evolve. This becomes particularly important when multiple agents and teams share the same tool ecosystem.
While
@Toolworks well for statically declared tools, I found it less suitable as the only abstraction for scenarios requiring runtime tool discovery, authorization, execution policies, and protection against recursive or nested tool invocation.Based on this, I built an experimental open-source project:
https://github.com/GreenDay1991/ai-tool-runtime
The approach is to keep Spring AI focused on the LLM ↔ Tool Calling layer, while introducing an independent runtime layer responsible for tool discovery, method resolution, secure tool creation, and runtime governance.
I’m interested in feedback on whether this separation of concerns could be useful for Spring AI applications, particularly in enterprise and multi-agent scenarios.
All reactions