local_ydb_remove_dynamic_nodes
Remove dynamic tenant suffix nodes one at a time and verify nodelist disappearance when the node IC port can be resolved. Without containers, nodeIds, or startIndex, only one-off suffixes above profile.dynamicNodeCount are eligible and the highest suffix is removed first. Explicit selectors or st...
This record as markdown: /tools/local-ydb/local-ydb-remove-dynamic-nodes.md
What local_ydb_remove_dynamic_nodes does on Local Ydb
AI agents call local_ydb_remove_dynamic_nodes to permanently remove resources in Local Ydb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why local_ydb_remove_dynamic_nodes is rated Critical
Irreversibly removes infrastructure nodes; state drift requires manual recovery via bootstrap or restart operations.
From the tool's definition Remove dynamic tenant suffix nodes one at a time; drift that bootstrap or restart restores.
Attacks that exploit this kind of access
The rule that runs local_ydb_remove_dynamic_nodes 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_remove_dynamic_nodes, this is the rule to start with:
local_ydb_remove_dynamic_nodes is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Local Ydb, apply this rule, and every local_ydb_remove_dynamic_nodes call is checked against it from then on.
Questions about local_ydb_remove_dynamic_nodes
Remove dynamic tenant suffix nodes one at a time and verify nodelist disappearance when the node IC port can be resolved. Without containers, nodeIds, or startIndex, only one-off suffixes above profile.dynamicNodeCount are eligible and the highest suffix is removed first. Explicit selectors or startIndex may remove a configured suffix and create drift that bootstrap or restart restores. Rollback guidance uses bootstrap/restart for configured nodes and add_dynamic_nodes with matching suffixes and ports for one-off nodes. The primary dynamicContainer is always protected. It is categorised as a Destructive tool in the Local Ydb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Local Ydb MCP server in PolicyLayer and add a rule for local_ydb_remove_dynamic_nodes: 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_remove_dynamic_nodes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the local_ydb_remove_dynamic_nodes 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_remove_dynamic_nodes. 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_remove_dynamic_nodes 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