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_
I am especially interested in the verify part of this, because here's how we develop tools for Open WebUI:
prompt via open webui
check tool calls
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
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
@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:
The more info we get in step 2 the better.