Tools turn assistants from advisors into actors — reading systems, posting data, sending communications. Admin Settings → Tools is where you register and govern those connections.
Register a tool server
1
Add Server
Admin Settings → Tools → Add Server.
2
Provide the connection
Enter the server URL and any credential the server requires. Servers expose their available functions automatically once connected.
3
Save and verify
Save. The server's tools become selectable in chat controls, templates and workflow nodes — subject to permissions.
Governance model
| Decision | How |
|---|---|
| Who may use tools | Permissions per group. |
| Which tools exist | Only servers you register here (plus any personal servers you allow — see Tools (user)). |
| What tools can reach | Your network policy decides — a tool server can only act on systems it is connected to. |
| How tools are used in flows | Workflow MCP Tool / Local Tools nodes. |
Treat tool servers as privileged:
A malicious or misconfigured tool server can do anything its credentials allow. Review each server before registering, grant it the minimum permissions, and document its owner. Prefer read-only connections where possible.
Reviewing tools
- Names and descriptions are what users see — keep them clear so people know what a tool does before enabling it.
- Unused servers should go — remove any server whose owning project or owner has changed.
- Monitor usage via Usage; unexpected consumption can indicate automation problems.