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; use after local_ydb_status_report for database-level diagnostics.
AI agents call local_ydb_healthcheck to retrieve information from Local Ydb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic queries against a YDB deployment to retrieve health status information. It has no side effects on the database or infrastructure—it only reads and reports health metrics.
From the tool's definition Tool description explicitly states 'Read-only YDB monitoring healthcheck' and 'returns selfCheckResult, issue counts, issue types, capped raw output, and whether the database is healthy'. No modification, deletion, or execution of code is performed.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
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; 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.
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.
local_ydb_healthcheck is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →