local_ydb_check_prerequisites
Check target-host prerequisites for the Docker CLI and daemon, curl, ruby, and the configured rootPasswordFile when present. An unreachable SSH target returns unavailable=[target] without claiming tools are missing or proposing installation. Without confirm=true it returns the current snapshot an...
This record as markdown: /tools/local-ydb/local-ydb-check-prerequisites.md
What local_ydb_check_prerequisites does on Local Ydb
AI agents call local_ydb_check_prerequisites 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_check_prerequisites is rated Low
Tool queries system prerequisites and optionally plans package installs without executing them; no data modification or destructive operations occur.
From the tool's definition Check target-host prerequisites for Docker CLI, daemon, curl, ruby
Attacks that exploit this kind of access
The rule that runs local_ydb_check_prerequisites 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_check_prerequisites, this is the rule to start with:
local_ydb_check_prerequisites 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_check_prerequisites call is checked against it from then on.
Questions about local_ydb_check_prerequisites
Check target-host prerequisites for the Docker CLI and daemon, curl, ruby, and the configured rootPasswordFile when present. An unreachable SSH target returns unavailable=[target] without claiming tools are missing or proposing installation. Without confirm=true it returns the current snapshot and any apt-get plan; confirm=true may install only supported curl/ruby packages, then returns a refreshed post-install snapshot, and never starts or installs Docker. 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_check_prerequisites: 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_check_prerequisites 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_check_prerequisites 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_check_prerequisites. 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_check_prerequisites 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