LeashIndex Get the report

Index / data

Local YDB MCP

io-github-astandrik-local-ydb-mcp declares 39 capabilities across 39 tools, with 2 critical issues.

94/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package @astandrik/local-ydb-mcp@0.19.0 (published to npm as @astandrik/local-ydb-mcp, listed in the official MCP registry as io.github.astandrik/local-ydb-mcp 0.19.0), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 39 tools

39 of 39 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 9 of 39 tools

9 tools are classified as irreversible and declare no limit.

high · no-expiry · All 39 tools

39 of 39 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 39 tools

39 of 39 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 13 of 39 tools

13 tools can modify data and declare no limit.

low · uncapped-read · 17 of 39 tools

17 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
local_ydb_inventoryread declared
local_ydb_database_statusread declared
local_ydb_healthcheckread declared
local_ydb_container_logsread declared
local_ydb_status_reportread declared
local_ydb_tenant_checkread declared
local_ydb_schemeread declared
local_ydb_generate_schemaread declared
local_ydb_apply_schemadestructive declared
local_ydb_sqldestructive declared
local_ydb_permissionsdestructive declared
local_ydb_nodes_checkread declared
local_ydb_graphshard_checkread declared
local_ydb_auth_checkread declared
local_ydb_storage_placementread declared
local_ydb_add_storage_groupswrite inferred
local_ydb_reduce_storage_groupsdestructive declared
local_ydb_storage_leftoversread declared
local_ydb_list_versionsread declared
local_ydb_pull_imagewrite assumed
local_ydb_pull_statusread declared
local_ydb_destroy_stackdestructive declared
local_ydb_bootstrap_root_databasewrite assumed
local_ydb_bootstrapwrite assumed
local_ydb_check_prerequisitesread inferred
local_ydb_create_tenantwrite inferred
local_ydb_start_dynamic_nodewrite assumed
local_ydb_add_dynamic_nodeswrite inferred
local_ydb_remove_dynamic_nodesdestructive declared
local_ydb_restart_stackwrite assumed
local_ydb_upgrade_versiondestructive declared
local_ydb_list_dumpsread declared
local_ydb_dump_tenantwrite assumed
local_ydb_restore_tenantdestructive declared
local_ydb_prepare_auth_configwrite assumed
local_ydb_write_dynamic_auth_configwrite inferred
local_ydb_apply_auth_hardeningwrite assumed
local_ydb_set_root_passwordwrite inferred
local_ydb_cleanup_storagedestructive declared
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.