github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-22 06:02:06 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

feat: Restrict tool usage #5741

New Issue
Closed
opened 2025-11-11 16:32:09 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 16:32:09 -06:00
Owner
Copy Link

Originally created by @yoyo-ouo on GitHub (Jul 11, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

I found that the model does not support disabling the use of tools. When I added the OpenAPI-compatible external tool server in the admin panel, even though I did not check the tool option in the model settings, I could still see the disabled tool during conversations, as shown in the image below: Image

This is not user-friendly for those who want strict control over permissions.

Additionally, I couldn't find any constraints regarding the use of the OpenAPI-compatible external tool server in the permission group settings.

Desired Solution you'd like

The model settings should allow for constraints on the use of tools, specifying which tools can be used and which cannot. Tools that are not allowed should be invisible during chats.

I would also like to have a disable unused tools feature, which would prevent users from disabling tools that have already been enabled in the settings. I believe this can help control the model's fixed capabilities. I would also like this feature to be customizable for each individual tool.

Note:

  1. Model settings refer to the admin panel’s configuration page for individual models, including parameters, knowledge bases, tools, capabilities, etc.
  2. The OpenAPI-compatible external tool server I’m using is MCPO.

Alternatives Considered

No response

Additional Context

No response

Originally created by @yoyo-ouo on GitHub (Jul 11, 2025). ### Check Existing Issues * [x] I have searched the existing issues and discussions. ### Problem Description I found that the model does not support disabling the use of tools. When I added the OpenAPI-compatible external tool server in the admin panel, even though I did not check the tool option in the model settings, I could still see the **disabled tool** during conversations, as shown in the image below: <img width="173" height="44" alt="Image" src="https://github.com/user-attachments/assets/05e60a1a-76e8-49be-a34b-4de2a410aca8" /> This is not user-friendly for those who want strict control over permissions. Additionally, I couldn't find any constraints regarding the use of the *OpenAPI-compatible external tool server* in the **permission group** settings. ### Desired Solution you'd like The model settings should allow for constraints on the use of tools, specifying which tools can be used and which cannot. Tools that are not allowed should be invisible during chats. I would also like to have a **disable unused tools** feature, which would prevent users from disabling tools that have already been enabled in the settings. I believe this can help control the model's fixed capabilities. I would also like this feature to be customizable for each individual tool. Note: 1. Model settings refer to the admin panel’s configuration page for individual models, including parameters, knowledge bases, tools, capabilities, etc. 2. The OpenAPI-compatible external tool server I’m using is MCPO. ### Alternatives Considered *No response* ### Additional Context *No response*
GiteaMirror commented 2025-11-11 16:32:10 -06:00
Author
Owner
Copy Link

@jack9603301 commented on GitHub (Jul 11, 2025):

这是国际社区，你就不能用英语吗？

@jack9603301 commented on GitHub (Jul 11, 2025): 这是国际社区，你就不能用英语吗？
GiteaMirror commented 2025-11-11 16:32:10 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jul 11, 2025):

Image
@tjbck commented on GitHub (Jul 11, 2025): <img width="537" height="636" alt="Image" src="https://github.com/user-attachments/assets/c16159cf-bca4-4a1b-9fe0-d42223a948ad" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#5741
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?