local_ydb_destroy_stack
Remove tenant metadata, local-ydb containers, network, and storage for a profile, with optional host-path cleanup.
This record as markdown: /tools/local-ydb/local-ydb-destroy-stack.md
What local_ydb_destroy_stack does on Local Ydb
AI agents call local_ydb_destroy_stack 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_destroy_stack is rated Critical
This tool permanently deletes multiple layers of infrastructure (containers, networks, storage, metadata) and cannot be undone. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' The blast radius is critical because an accidental invocation would destroy an entire local deployment environment and its…
From the tool's definition Tool name contains 'destroy'; description states 'Remove tenant metadata, local-ydb containers, network, and storage' — irreversible deletion of infrastructure, data, and configuration.
Attacks that exploit this kind of access
The rule that runs local_ydb_destroy_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_destroy_stack, this is the rule to start with:
local_ydb_destroy_stack 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_destroy_stack call is checked against it from then on.
Questions about local_ydb_destroy_stack
Remove tenant metadata, local-ydb containers, network, and storage for a profile, with optional host-path cleanup. 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_destroy_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_destroy_stack 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_destroy_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_destroy_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_destroy_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