local_ydb_remove_dynamic_nodes

Remove extra dynamic tenant nodes one at a time and verify nodelist disappearance when the node IC port can be resolved.

SERVERLocal Ydb SOURCE@astandrik/local-ydb-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/local-ydb/local-ydb-remove-dynamic-nodes.md

WHAT IT DOES

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.

RISK

Why local_ydb_remove_dynamic_nodes is rated Critical

Removing dynamic tenant nodes from a running YDB cluster is a destructive action: once nodes are removed, any workloads or sessions on those nodes are terminated and the capacity is lost. While nodes could theoretically be re-added, the removal itself is not undoable — it eliminates running processes and their state. The phrase 'verify nodelist disappearance' confirms the intent is permanent removal, not a soft stop.

From the tool's definition 'Remove extra dynamic tenant nodes one at a time and verify nodelist disappearance' — removing nodes is an irreversible infrastructure operation that eliminates active compute resources from the YDB deployment.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Hidden

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "local_ydb_remove_dynamic_nodes"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about local_ydb_remove_dynamic_nodes

What does the local_ydb_remove_dynamic_nodes tool do? +

Remove extra dynamic tenant nodes one at a time and verify nodelist disappearance when the node IC port can be resolved. 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.

How do I enforce a policy on local_ydb_remove_dynamic_nodes? +

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.

What risk level is local_ydb_remove_dynamic_nodes? +

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.

Can I rate-limit local_ydb_remove_dynamic_nodes? +

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.

How do I block local_ydb_remove_dynamic_nodes completely? +

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.

What MCP server provides local_ydb_remove_dynamic_nodes? +

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.

KEEP EXPLORING

More on Local Ydb, and thousands of servers like it.

This server

All 38 Local Ydb tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →