Model Context Protocol moderate risk

Ydb

YDB MCP enables LLMs to interact with YDB databases using natural language, supporting queries, data manipulation, and database management via the Model Context Protocol.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwriteexec

Quickstart

Install

pip install ydb-mcp

Config

{
  "mcpServers": {
    "ydb": {
      "command": "uvx",
      "args": [
        "ydb-mcp",
        "--ydb-endpoint", "grpc://localhost:2136",
        "--ydb-database", "/local"
      ]
    }
  }
}

Exposed MCP Tools (5)

moderate

ydb_query

Executes a SQL query against the YDB database.

Allows arbitrary SQL queries, potentially modifying data.

moderate

ydb_query_with_params

Executes a parameterized SQL query with JSON parameters.

Allows data modification through parameterized SQL queries.

safe

ydb_list_directory

Lists the contents of a directory in YDB.

Read-only operation, no data modification.

safe

ydb_describe_path

Retrieves detailed information about a specific path in YDB.

Read-only operation, no data modification.

safe

ydb_status

Gets the current status of the YDB connection.

Read-only operation, provides connection status.

Safety Assessment

YDB MCP offers a balance between functionality and security. While it allows write operations, the availability of authentication methods and a defined toolset provide some control. However, the absence of explicit sandboxing and the potential for SQL injection if parameterized queries aren't used correctly necessitate careful configuration and usage.

Authentication options available (login/password, token, service account)
Clear separation of concerns via MCP
Well-defined tool set limits scope of actions
Supports parameterized queries to prevent SQL injection

Write operations possible, increasing risk of data modification
Improperly configured authentication can lead to unauthorized access
No explicit sandboxing mentioned, relying on YDB's internal security
Potential for SQL injection if parameterized queries are not used correctly
Lack of rate limiting could lead to resource exhaustion