Create a knowledge base in Open WebUI
AI agents use owui_create_knowledge to create or update resources in ML Lab MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ML Lab MCP environment.
This tool creates a new knowledge base, which is a reversible write operation. It modifies the state of the Open WebUI system by adding a new resource, but does not execute arbitrary code, delete data, or commit financial transactions. The severity is medium because a malicious actor could create unwanted knowledge bases consuming resources, but this is not as severe as Execute or Destructive operations.
From the tool's definition Tool name includes 'create' and description states 'Create a knowledge base in Open WebUI', which is a data creation operation.
Attacks that exploit this kind of access
Create a knowledge base in Open WebUI. It is categorised as a Write tool in the ML Lab MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ML Lab MCP server in PolicyLayer and add a rule for owui_create_knowledge: 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 ML Lab MCP. Nothing to install.
owui_create_knowledge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the owui_create_knowledge 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 owui_create_knowledge. 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.
owui_create_knowledge is provided by the ML Lab MCP server (pushpullcommitpush/ml-mcp). 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 →