local_ydb_cleanup_storage
Delete only the explicitly supplied local-ydb host paths or Docker volumes. Use after inspecting local_ydb_storage_leftovers; without confirm=true this returns the cleanup plan and removes nothing.
This record as markdown: /tools/local-ydb/local-ydb-cleanup-storage.md
What local_ydb_cleanup_storage does on Local Ydb
AI agents call local_ydb_cleanup_storage 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_cleanup_storage is rated Critical
This tool permanently deletes data from storage paths or Docker volumes. While it includes a safeguard (requires confirm=true to actually execute, and returns a plan first), the core function is irreversible destruction of data. This is clearly destructive rather than write (which is reversible) or execute (which may have variable effects).
From the tool's definition 'Delete only the explicitly supplied local-ydb host paths or Docker volumes' — the tool explicitly performs deletion of storage paths/volumes, which is irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs local_ydb_cleanup_storage 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_cleanup_storage, this is the rule to start with:
local_ydb_cleanup_storage 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_cleanup_storage call is checked against it from then on.
Questions about local_ydb_cleanup_storage
Delete only the explicitly supplied local-ydb host paths or Docker volumes. Use after inspecting local_ydb_storage_leftovers; without confirm=true this returns the cleanup plan and removes nothing. 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_cleanup_storage: 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_cleanup_storage 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_cleanup_storage 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_cleanup_storage. 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_cleanup_storage 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