Critical Risk →

local_ydb_destroy_stack

Remove tenant metadata, local-ydb containers, network, and storage for a profile, with optional host-path cleanup.

Part of the Local Ydb MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call local_ydb_destroy_stack to permanently remove or destroy resources in Local Ydb. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call local_ydb_destroy_stack in a loop, permanently destroying resources in Local Ydb. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

local-ydb.yaml
tools:
  local_ydb_destroy_stack:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Local Ydb policy for all 34 tools.

Tool Name local_ydb_destroy_stack
Category Destructive
Risk Level Critical

View all 34 tools →

Agents calling destructive-class tools like local_ydb_destroy_stack have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

local_ydb_destroy_stack is one of the critical-risk operations in Local Ydb. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the local_ydb_destroy_stack tool do? +

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.

How do I enforce a policy on local_ydb_destroy_stack? +

Add a rule in your Intercept YAML policy under the tools section for local_ydb_destroy_stack. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Local Ydb MCP server.

What risk level is local_ydb_destroy_stack? +

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.

Can I rate-limit local_ydb_destroy_stack? +

Yes. Add a rate_limit block to the local_ydb_destroy_stack rule in your Intercept 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_destroy_stack completely? +

Set action: deny in the Intercept 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.

What MCP server provides local_ydb_destroy_stack? +

local_ydb_destroy_stack is provided by the Local Ydb MCP server (@astandrik/local-ydb-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.