local_ydb_restore_tenant

SERVERLocal Ydb SOURCE@astandrik/local-ydb-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/local-ydb/local-ydb-restore-tenant.md

WHAT IT DOES

What local_ydb_restore_tenant does on Local Ydb

AI agents use local_ydb_restore_tenant to create or update resources in Local Ydb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Ydb environment.

RISK

Why local_ydb_restore_tenant is rated Medium

This tool restores data from a dump, which is a reversible write operation that modifies the tenant's state. While the tool includes safeguards (optional confirm parameter, dry-run capability via confirm=false), executing a restore operation writes substantial amounts of data into a live database and could overwrite existing schema and data.

From the tool's definition 'Restore the configured tenant or destination path from a dump' — this tool restores data from a dump file, which writes data into the target tenant/database.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs local_ydb_restore_tenant 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_restore_tenant, this is the rule to start with:

local_ydb_restore_tenant Rate-limited

local_ydb_restore_tenant stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "local_ydb_restore_tenant": {
      "limits": [
        {
          "counter": "local_ydb_restore_tenant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_restore_tenant call is checked against it from then on.

FAQ

Questions about local_ydb_restore_tenant

What does the local_ydb_restore_tenant tool do? +

Restore the configured tenant or destination path from a dump under profile.dumpHostPath, with optional post-restore scheme describe and bounded count-query verification. Use after bootstrap or rebuild when the target tenant is ready; without confirm=true this returns the restore plan and does not write data. It is categorised as a Write tool in the Local Ydb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on local_ydb_restore_tenant? +

Register the Local Ydb MCP server in PolicyLayer and add a rule for local_ydb_restore_tenant: 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_restore_tenant? +

local_ydb_restore_tenant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit local_ydb_restore_tenant? +

Yes. Add a rate_limit block to the local_ydb_restore_tenant 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_restore_tenant completely? +

Set action: deny in the PolicyLayer policy for local_ydb_restore_tenant. 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_restore_tenant? +

local_ydb_restore_tenant 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →