AI agents call get_chat to retrieve information from Open WebUI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing chat data and message history without modifying, creating, or deleting any resources. It is a straightforward read operation with minimal blast radius—the worst outcome of misuse would be unauthorized information disclosure of existing chat content, which is less severe than write, execute, or destructive operations.
From the tool's definition Tool name 'get_chat' with description 'Get a chat's details and message history' indicates pure retrieval with 'Get' verb and no side effects (no create, modify, or delete operations).
Documented attack patterns abuse exactly the kind of access get_chat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open WebUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_chat:
{
"version": "1",
"default": "deny",
"tools": {
"get_chat": {}
}
}get_chat is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a chat's details and message history. It is categorised as a Read tool in the Open WebUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Open WebUI MCP Server MCP server in PolicyLayer and add a rule for get_chat: 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 MCP Server. Nothing to install.
get_chat 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 get_chat 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 get_chat. 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.
get_chat is provided by the Open WebUI MCP Server MCP server (troylar/open-webui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Open WebUI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
82 Open WebUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.