Model Context Protocol moderate risk

Hydrolix

The Hydrolix MCP server enables LLMs to query and manage Hydrolix data through SQL, with authentication via tokens or credentials.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readwriteexec

Quickstart

Config

{
  "command": "uv",
  "args": [
    "run",
    "--with",
    "mcp-hydrolix",
    "--python",
    "3.13",
    "mcp-hydrolix"
  ],
  "env": {
    "HYDROLIX_HOST": "<hydrolix-host>",
    "HYDROLIX_USER": "<hydrolix-user>",
    "HYDROLIX_PASSWORD": "<hydrolix-password>"
  }
}

Exposed MCP Tools (4)

high

run_select_query

Executes a SQL query against the Hydrolix database.

Allows execution of arbitrary SQL, potentially leading to data modification or leakage.

safe

list_databases

Lists all databases available on the Hydrolix cluster.

Read-only operation that does not modify data.

safe

list_tables

Lists all tables within a specified database.

Read-only operation that does not modify data.

safe

get_table_info

Retrieves metadata, such as schema, for a specified table.

Read-only operation that does not modify data.

Safety Assessment

The Hydrolix MCP server offers a balance of functionality and security. Using a read-only service account token and keeping SSL verification enabled minimizes risks. However, the ability to execute arbitrary SQL queries means that a compromised service account could still be used to access sensitive data.

Supports read-only service account tokens
Authentication required via token or username/password
SSL certificate verification enabled by default
Can be configured to run on a private network interface

Can execute arbitrary SQL queries
Potential for data exfiltration if service account is compromised
Per-request authentication via GET parameter can expose tokens in logs
Disabling SSL certificate verification is possible