local_ydb_restart_stack
Reconcile and restart the selected profile after inventory and a full check-only static compatibility preflight. Before stopping any container, require the existing static container to match the profile image, network, data mount, environment, restart policy, healthcheck, and exact loopback bindi...
This record as markdown: /tools/local-ydb/local-ydb-restart-stack.md
What local_ydb_restart_stack does on Local Ydb
AI agents invoke local_ydb_restart_stack to trigger actions in Local Ydb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why local_ydb_restart_stack is rated High
Restarts and reconciles containers, stopping and recreating them in a specific order.
From the tool's definition reconcile and restart the selected profile, stop running containers
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs local_ydb_restart_stack 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_restart_stack, this is the rule to start with:
local_ydb_restart_stack stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_restart_stack call is checked against it from then on.
Questions about local_ydb_restart_stack
Reconcile and restart the selected profile after inventory and a full check-only static compatibility preflight. Before stopping any container, require the existing static container to match the profile image, network, data mount, environment, restart policy, healthcheck, and exact loopback bindings for static gRPC, monitoring, and every configured dynamic gRPC port; configured binding changes require destroy followed by bootstrap. Then report missing configured and unexpected one-off dynamic containers, stop running dynamic containers before static, unconditionally recreate every configured node in index order including containers observed restarting, require each exact Docker container to be stably running plus registered by IC port, and restore only previously running unexpected containers without removing them. Because removed configured definitions cannot be recovered from inventory, rollback uses restart or bootstrap reconciliation. Without confirm=true this returns the restart plan only. It is categorised as a Execute tool in the Local Ydb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Ydb MCP server in PolicyLayer and add a rule for local_ydb_restart_stack: 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_restart_stack is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the local_ydb_restart_stack 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_restart_stack. 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_restart_stack 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.
Across the catalogue