local_ydb_healthcheck

SERVERLocal Ydb SOURCE@astandrik/local-ydb-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/local-ydb/local-ydb-healthcheck.md

WHAT IT DOES

What local_ydb_healthcheck does on Local Ydb

AI agents call local_ydb_healthcheck to retrieve information from Local Ydb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why local_ydb_healthcheck is rated Low

Tool queries database health status without modifying data or triggering external operations.

From the tool's definition Read-only YDB monitoring healthcheck, SelfCheck path, returns selfCheckResult

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs local_ydb_healthcheck safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local Ydb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For local_ydb_healthcheck, this is the rule to start with:

local_ydb_healthcheck Allowed

local_ydb_healthcheck is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "local_ydb_healthcheck": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local Ydb, apply this rule, and every local_ydb_healthcheck call is checked against it from then on.

FAQ

Questions about local_ydb_healthcheck

What does the local_ydb_healthcheck tool do? +

Read-only YDB monitoring healthcheck for the configured tenant or root database. Uses the official YDB CLI SelfCheck path, returns selfCheckResult, issue counts, issue types, capped raw output, and whether the database is healthy; a requested noCache/noMerge option rejected with the exact recognized two-line legacy parser signature is reported through optionResolution and warnings, while compatibilityFallback says whether a retry actually started. Use after local_ydb_status_report for database-level diagnostics. It is categorised as a Read tool in the Local Ydb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on local_ydb_healthcheck? +

Register the Local Ydb MCP server in PolicyLayer and add a rule for local_ydb_healthcheck: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Local Ydb. Nothing to install.

What risk level is local_ydb_healthcheck? +

local_ydb_healthcheck is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit local_ydb_healthcheck? +

Yes. Add a rate_limit block to the local_ydb_healthcheck rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block local_ydb_healthcheck completely? +

Set action: deny in the PolicyLayer policy for local_ydb_healthcheck. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides local_ydb_healthcheck? +

local_ydb_healthcheck is provided by the Local Ydb MCP server (@astandrik/local-ydb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local Ydb, and thousands of servers like it.

This server

All 39 Local Ydb tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →