List all knowledge bases accessible via Open WebUI API
AI agents call list_knowledge_bases to retrieve information from Open WebUI Knowledge Base MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available knowledge bases without creating, modifying, deleting, or executing operations. It is a pure read operation with minimal blast radius if misused by an AI agent—at most, it reveals what knowledge bases exist in the system.
From the tool's definition Tool name 'list_knowledge_bases' and description 'List all knowledge bases accessible via Open WebUI API' indicate a retrieval operation with no data modification.
Attacks that exploit this kind of access
List all knowledge bases accessible via Open WebUI API. It is categorised as a Read tool in the Open WebUI Knowledge Base MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Open WebUI Knowledge Base MCP Server MCP server in PolicyLayer and add a rule for list_knowledge_bases: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Open WebUI Knowledge Base MCP Server. Nothing to install.
list_knowledge_bases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_knowledge_bases rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_knowledge_bases. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_knowledge_bases is provided by the Open WebUI Knowledge Base MCP Server MCP server (ronasit/open-webui-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →