check_open_webui

Check Open WebUI (Ollama/LLM frontend) health via GET /health. Returns healthy status. Default port 3000.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-open-webui.md

WHAT IT DOES

What check_open_webui does on Mcp Nettools

AI agents call check_open_webui to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_open_webui is rated Low

This tool retrieves health status information from an Open WebUI service via a simple HTTP GET request to a standard health check endpoint. It has no side effects, cannot modify data, and poses minimal security risk. The operation is informational only, making it a Read category tool with low severity.

From the tool's definition Tool description states it performs a GET request to /health endpoint, which is a read-only health check operation. No modification, deletion, or execution of code is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_open_webui safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_open_webui, this is the rule to start with:

check_open_webui Allowed

check_open_webui is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_open_webui": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_open_webui call is checked against it from then on.

FAQ

Questions about check_open_webui

What does the check_open_webui tool do? +

Check Open WebUI (Ollama/LLM frontend) health via GET /health. Returns healthy status. Default port 3000. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_open_webui? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_open_webui: 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 Mcp Nettools. Nothing to install.

What risk level is check_open_webui? +

check_open_webui is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_open_webui? +

Yes. Add a rate_limit block to the check_open_webui 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.

How do I block check_open_webui completely? +

Set action: deny in the PolicyLayer policy for check_open_webui. 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.

What MCP server provides check_open_webui? +

check_open_webui is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →