// SCAN REPORT

Local Ydb

34 tools. 14 can modify or destroy data without limits.

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

Last updated: 6 May 2026

14 can modify or destroy data

20 read-only

34 tools total

// TOOL MAP

Read (20) Write / Execute (10) Destructive / Financial (4)

// WHAT CAN GO WRONG

Destructive tools (local_ydb_cleanup_storage, local_ydb_destroy_stack, local_ydb_permissions) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (local_ydb_add_dynamic_nodes, local_ydb_add_storage_groups, local_ydb_apply_auth_hardening) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (local_ydb_pull_image, local_ydb_restart_stack, local_ydb_start_dynamic_node) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

// RECOMMENDED RULES

Deny destructive operations

local_ydb_cleanup_storage:
  rules:
    - action: deny

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

Rate limit write operations

local_ydb_add_dynamic_nodes:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

local_ydb_auth_check:
  rules:
    - rate_limit: 60/minute

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

// ALL 34 LOCAL YDB TOOLS

DESTRUCTIVE 4 tools

Destructive local_ydb_cleanup_storage Destructive local_ydb_destroy_stack Destructive local_ydb_permissions Destructive local_ydb_remove_dynamic_nodes

EXECUTE 3 tools

Execute local_ydb_pull_image Execute local_ydb_restart_stack Execute local_ydb_start_dynamic_node

WRITE 7 tools

Write local_ydb_add_dynamic_nodes Write local_ydb_add_storage_groups Write local_ydb_apply_auth_hardening Write local_ydb_create_tenant Write local_ydb_restore_tenant Write local_ydb_set_root_password Write local_ydb_write_dynamic_auth_config

// FAQ

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

Yes. The Local Ydb server exposes 4 destructive tools including local_ydb_cleanup_storage, local_ydb_destroy_stack, local_ydb_permissions. These permanently remove resources with no undo. Intercept 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 7 write tools including local_ydb_add_dynamic_nodes, local_ydb_add_storage_groups, local_ydb_apply_auth_hardening. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

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

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

How do I add Intercept to my Local Ydb setup? +

One line change. Instead of running the Local Ydb server directly, prefix it with Intercept: intercept -c local-ydb.yaml -- npx -y @@astandrik/local-ydb-mcp. Download a pre-built policy from policylayer.com/policies/local-ydb and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Local Ydb

Other MCP servers with similar tools.

Let agents act without letting them run wild.