// SCAN REPORT

Local Ydb

38 tools. 20 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

20 can modify or destroy data

18 read-only

38 tools total

Community server · catalogue entry checked 29/06/2026

How to control Local Ydb ↓

TOOL MAP

What Local Ydb exposes to your agents

Read (18) Write / Execute (17) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Local Ydb tools

Destructive · High local_ydb_cleanup_storage This tool permanently deletes data from storage paths or Docker volumes. Destructive · Critical local_ydb_destroy_stack This tool permanently deletes multiple layers of infrastructure (containers, networks, storage, metadata) and cannot be undone. Destructive · High local_ydb_remove_dynamic_nodes Removing dynamic tenant nodes from a running YDB cluster is a destructive action: once nodes are removed, any workloads or sessions on those nodes are terminated and the capacity is lost. Execute · High local_ydb_start_dynamic_node This tool executes infrastructure management commands that start database nodes.

20 of Local Ydb's 38 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Local Ydb

PolicyLayer is an MCP gateway — it sits between your AI agents and Local Ydb, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "local_ydb_cleanup_storage": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "local_ydb_add_storage_groups": {
    "limits": [
      {
        "counter": "local_ydb_add_storage_groups_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "local_ydb_auth_check": {
    "limits": [
      {
        "counter": "local_ydb_auth_check_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Local Ydb — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LOCAL YDB →

Instant setup, no code required.

FULL CATALOGUE

All 38 Local Ydb tools

DESTRUCTIVE 3 tools

Destructive local_ydb_cleanup_storage Delete only the explicitly supplied local-ydb host paths or Docker volumes. Use after inspecting local_ydb_sto Destructive local_ydb_destroy_stack Remove tenant metadata, local-ydb containers, network, and storage for a profile, with optional host-path clea Destructive local_ydb_remove_dynamic_nodes Remove extra dynamic tenant nodes one at a time and verify nodelist disappearance when the node IC port can be

EXECUTE 9 tools

Execute local_ydb_add_dynamic_nodes Add extra dynamic tenant nodes beyond the configured primary dynamic node, one at a time. Without confirm=true Execute local_ydb_apply_auth_hardening Apply a reviewed hardened YDB config file and restart local-ydb so auth settings take effect. Use only after p Execute local_ydb_bootstrap Bootstrap a tenant topology: static node with GraphShard flags, configured CMS tenant, and primary dynamic ten Execute local_ydb_bootstrap_root_database Bootstrap a plain local YDB database at /local with only a static node. Use for generic local database request Execute local_ydb_check_prerequisites Check target-host prerequisites for Docker, curl, ruby, and the configured rootPasswordFile when present. With Execute local_ydb_pull_image Plan or start a background Docker pull for a local-ydb image on the selected target. Without confirm=true it r Execute local_ydb_restart_stack Restart the selected profile by stopping dynamic and static containers, starting the static node, ensuring the Execute local_ydb_start_dynamic_node Start the configured primary dynamic tenant node for an existing CMS tenant. Use after local_ydb_create_tenant Execute local_ydb_upgrade_version Upgrade a file-backed, volume-backed local-ydb profile to a target image tag. Use only for version upgrades on

WRITE 8 tools

Write local_ydb_add_storage_groups Increase NumGroups for one tenant storage pool using the current ReadStoragePool definition. Without confirm=t Write local_ydb_apply_schema Validate or apply YDB table DDL through the official YDB JS SDK. It accepts raw YQL DDL for PRAGMA plus CREATE Write local_ydb_create_tenant Create the configured CMS tenant when the static node is already running. Use before local_ydb_start_dynamic_n Write local_ydb_permissions Inspect or change YDB scheme permissions for a path. The default list action is read-only; grant, revoke, set, Write local_ydb_prepare_auth_config Generate a hardened YDB config from the current static-node config. Use before local_ydb_write_dynamic_auth_co Write local_ydb_restore_tenant Restore the configured tenant or destination path from a dump under profile.dumpHostPath, with optional post-r Write local_ydb_set_root_password Rotate the runtime root password with ALTER USER and sync the host auth config and root password file to match Write local_ydb_write_dynamic_auth_config Write the text-proto dynamic-node auth token file needed for mandatory-auth startup. Use after choosing the SI

READ 18 tools

Read local_ydb_auth_check Read-only auth audit that checks anonymous viewer whoami status and configured YDB CLI tenant access, using ro Read local_ydb_container_logs Read recent Docker logs from the configured static or primary dynamic local-ydb container. Use when bootstrap, Read local_ydb_database_status Read-only YDB admin database status for the configured tenant path. Returns the command, stdout, stderr, and o Read local_ydb_dump_tenant Dump the configured tenant or a tenant-relative path using a local-ydb helper container on the static containe Read local_ydb_generate_schema Read-only structured YDB table DDL generator. It renders strict JSON specs for CREATE TABLE, ALTER TABLE, DROP Read local_ydb_graphshard_check Read-only GraphShard check through viewer/json capabilities and tabletinfo for the configured tenant. Returns Read local_ydb_healthcheck Read-only YDB monitoring healthcheck for the configured tenant or root database. Uses the official YDB CLI Sel Read local_ydb_inventory Read-only Docker inventory for a local-ydb target profile. Returns the public profile, Docker containers and v Read local_ydb_list_dumps Read-only list of available tenant dumps under profile.dumpHostPath. Use before restore to choose a dumpName; Read local_ydb_list_versions List published registry tags for a local-ydb container image, with numeric version tags sorted newest first. U Read local_ydb_nodes_check Read-only check of dynamic node registration through viewer/json nodelist. Use after starting, adding, or remo Read local_ydb_pull_status Check the status of a background Docker image pull started by local_ydb_pull_image. Read local_ydb_reduce_storage_groups Reduce NumGroups for a tenant storage pool by dumping the tenant, rebuilding the profile stack with a smaller Read local_ydb_scheme Read-only YDB scheme list or describe with capped stdout/stderr. It uses the root database for rootDatabase pa Read local_ydb_status_report Read-only aggregate report for quick diagnosis. Runs local_ydb_inventory, local_ydb_auth_check, local_ydb_tena Read local_ydb_storage_leftovers Read-only search for candidate leftover local-ydb Docker volumes, dumps, and PDisk/data paths. It scans Docker Read local_ydb_storage_placement Read-only storage inspection that returns ReadStoragePool output and BSC physical placement. Use before adding Read local_ydb_tenant_check Read-only check that uses the YDB CLI to verify the configured tenant path is reachable. Use after bootstrap o

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Local Ydb

Can an AI agent delete data through the Local Ydb MCP server? +

Yes. The Local Ydb server exposes 3 destructive tools including local_ydb_cleanup_storage, local_ydb_destroy_stack, local_ydb_remove_dynamic_nodes. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Local Ydb? +

The Local Ydb server has 8 write tools including local_ydb_add_storage_groups, local_ydb_apply_schema, local_ydb_create_tenant. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Local Ydb.

How many tools does the Local Ydb MCP server expose? +

38 tools across 4 categories: Destructive, Execute, Read, Write. 18 are read-only. 20 can modify, create, or delete data.

How do I enforce a policy on Local Ydb? +

Register the Local Ydb MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Local Ydb tool call.

Deterministic rules across all 38 Local Ydb tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LOCAL YDB →

Instant setup, no code required.

38 Local Ydb tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Local Ydb's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →