github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #16940] feat: Confirming inputs passed to MCP/tools #56770

New Issue
Open
opened 2026-05-05 20:05:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-05 20:05:13 -05:00
Owner
Copy Link

Originally created by @jayteaftw on GitHub (Aug 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16940

Originally assigned to: @tjbck on GitHub.

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

I want to be able to determine what data the LLM wants to send out to search the web and if I dont want the data to be sent then I can either cancel the request or if possible be able to modify it.

Desired Solution you'd like

I would like to be able to verify what data is being sent to MCP tools and be able to confirm or cancel a MCP tool request.

Is this currently possible with filter? If so where is it being shown within the inlet function for a filter? It seems to be the case that inlet data is before the actual tool call is made

Alternatives Considered

Is there a way to do this with the current filters?

Additional Context

No response

Originally created by @jayteaftw on GitHub (Aug 26, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16940 Originally assigned to: @tjbck on GitHub. ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description I want to be able to determine what data the LLM wants to send out to search the web and if I dont want the data to be sent then I can either cancel the request or if possible be able to modify it. ### Desired Solution you'd like I would like to be able to verify what data is being sent to MCP tools and be able to confirm or cancel a MCP tool request. Is this currently possible with filter? If so where is it being shown within the inlet function for a filter? It seems to be the case that inlet data is before the actual tool call is made ### Alternatives Considered Is there a way to do this with the current filters? ### Additional Context _No response_
GiteaMirror commented 2026-05-05 20:05:17 -05:00
Author
Owner
Copy Link

@felixhummel commented on GitHub (Aug 28, 2025):

I am especially interested in the verify part of this, because here's how we develop tools for Open WebUI:

  1. prompt via open webui
  2. check tool calls
  3. edit our API

The more info we get in step 2 the better.

<!-- gh-comment-id:3233335516 --> @felixhummel commented on GitHub (Aug 28, 2025): I am especially interested in the **verify** part of this, because here's how we develop tools for Open WebUI: 1. prompt via open webui 2. check tool calls 3. edit our API The more info we get in step 2 the better.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
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#56770
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?