Tool Groups
Name a set of related tools so forty imported endpoints behave like one thing you can reason about.
A tool group is a name for a set of related tools. It exists mostly because importing an OpenAPI spec can create dozens of tools at once, and a flat list of forty endpoints is not something anyone can work with.
Groups are managed on the Tools screen: pick or create one in a tool's Group field, and each OpenAPI import creates its own. Each custom tool belongs to at most one.
What groups are for
- Assigning. Tick a group when configuring an agent instead of ticking its members one at a time.
- Reading. The tools list stays navigable when one vendor's API contributes forty entries.
- Auditing. "Which agents can reach the billing API" is a question about a group.
Deleting a group
Deleting a group does not delete its tools — they stay and become ungrouped. The group is a label, not a container, and losing a label should never lose the thing it was on.
Groups are not a permission boundary
A group is organisational. It does not restrict what its tools may do, and putting a dangerous tool in a group named "read-only" changes nothing.
What an agent may actually do with the tools it holds is tool policy, which decides per call and by declared behaviour rather than by name.