local_ydb_reduce_storage_groups
Reduce NumGroups for a tenant storage pool by dumping the tenant, rebuilding the profile stack with a smaller storagePoolCount, restoring the dump, and reapplying auth when needed. Before dump or destroy, it inspects every one-off dynamic node and preserves its exact gRPC, monitoring, and IC port...
This record as markdown: /tools/local-ydb/local-ydb-reduce-storage-groups.md
What local_ydb_reduce_storage_groups does on Local Ydb
AI agents call local_ydb_reduce_storage_groups 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_reduce_storage_groups is rated Critical
Reduces storage groups through dumping and rebuilding; data loss risk if incomplete definition causes abort during critical rebuild phase.
From the tool's definition dumping tenant, rebuilding profile stack, destroying, irreversible storage group reduction
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs local_ydb_reduce_storage_groups 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_reduce_storage_groups, this is the rule to start with:
local_ydb_reduce_storage_groups 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_reduce_storage_groups call is checked against it from then on.
Questions about local_ydb_reduce_storage_groups
Reduce NumGroups for a tenant storage pool by dumping the tenant, rebuilding the profile stack with a smaller storagePoolCount, restoring the dump, and reapplying auth when needed. Before dump or destroy, it inspects every one-off dynamic node and preserves its exact gRPC, monitoring, and IC ports; an incomplete definition aborts the rebuild. 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_reduce_storage_groups: 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_reduce_storage_groups 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_reduce_storage_groups 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_reduce_storage_groups. 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_reduce_storage_groups 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