check_clickhouse

Check ClickHouse OLAP database availability via HTTP /ping endpoint. Returns 'Ok.' on success. Port 8123 = HTTP interface, 8443 = HTTPS. Also returns version from the response header.

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-clickhouse.md

WHAT IT DOES

What check_clickhouse does on Mcp Nettools

AI agents call check_clickhouse 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_clickhouse is rated Low

This tool only queries the health status of a remote service via a standard HTTP ping endpoint. It retrieves information (availability status and version) without side effects. No data is modified, deleted, executed, or financially impacted. This is a diagnostic read operation consistent with the 'network diagnostics' purpose of the mcp-nettools server.

From the tool's definition Tool performs a /ping endpoint check against a ClickHouse database to verify availability and retrieve version information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_clickhouse 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_clickhouse, this is the rule to start with:

check_clickhouse Allowed

check_clickhouse 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_clickhouse": {}
  }
}

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_clickhouse call is checked against it from then on.

FAQ

Questions about check_clickhouse

What does the check_clickhouse tool do? +

Check ClickHouse OLAP database availability via HTTP /ping endpoint. Returns 'Ok.' on success. Port 8123 = HTTP interface, 8443 = HTTPS. Also returns version from the response header. 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_clickhouse? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_clickhouse: 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_clickhouse? +

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

Can I rate-limit check_clickhouse? +

Yes. Add a rate_limit block to the check_clickhouse 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_clickhouse completely? +

Set action: deny in the PolicyLayer policy for check_clickhouse. 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_clickhouse? +

check_clickhouse 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 →