local_ydb_restart_stack
Restart the selected profile by stopping dynamic and static containers, starting the static node, ensuring the configured tenant, then starting the dynamic node. Use after config or runtime changes; without confirm=true this returns the restart plan only.
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
This tool executes infrastructure management commands that restart containers and services. While not permanently destructive, restarting services is an Execute category action because it triggers external operations (container stop/start, node initialization) with effects that depend on the tool's arguments (profile selection, configuration). The tool can disrupt running workloads and cause temporary unavailability.
From the tool's definition "Restart the selected profile by stopping dynamic and static containers, starting the static node" - this tool orchestrates container lifecycle operations (stop, start) which are external operations whose effects depend on which profile is selected and the…
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
Restart the selected profile by stopping dynamic and static containers, starting the static node, ensuring the configured tenant, then starting the dynamic node. Use after config or runtime changes; 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