local_ydb_status_report
Read-only aggregate report for quick diagnosis. Runs local_ydb_inventory, local_ydb_auth_check, local_ydb_tenant_check, local_ydb_nodes_check, and local_ydb_healthcheck, returning each result; use this first for broad stack health, then run focused checks for database status, GraphShard, storage,...
This record as markdown: /tools/local-ydb/local-ydb-status-report.md
What local_ydb_status_report does on Local Ydb
AI agents call local_ydb_status_report 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.
Why local_ydb_status_report is rated Low
This tool retrieves and aggregates system status information without modifying any state. It performs query and diagnostic operations only, with no side effects. The explicit 'read-only' designation and the nature of its constituent checks (inventory, health checks, status checks) confirm it belongs in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Read-only aggregate report' and lists sub-operations that are diagnostic checks: inventory, auth_check, tenant_check, nodes_check, and healthcheck.
Attacks that exploit this kind of access
The rule that runs local_ydb_status_report 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_status_report, this is the rule to start with:
local_ydb_status_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local Ydb, apply this rule, and every local_ydb_status_report call is checked against it from then on.
Questions about local_ydb_status_report
Read-only aggregate report for quick diagnosis. Runs local_ydb_inventory, local_ydb_auth_check, local_ydb_tenant_check, local_ydb_nodes_check, and local_ydb_healthcheck, returning each result; use this first for broad stack health, then run focused checks for database status, GraphShard, storage, or logs. 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_status_report: 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_status_report 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_status_report 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_status_report. 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_status_report 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.
More on Local Ydb, and thousands of servers like it.
This server
Across the catalogue