local_ydb_dump_tenant

Dump the configured tenant or a tenant-relative path using a local-ydb helper container on the static container network. It creates profile.dumpHostPath/dumpName, excludes .sys objects, writes the dump under dumpName/tenant, and without confirm=true returns the mkdir/helper-container plan only.

SERVERLocal Ydb SOURCE@astandrik/local-ydb-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What local_ydb_dump_tenant does on Local Ydb

AI agents call local_ydb_dump_tenant to retrieve information from Local Ydb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why local_ydb_dump_tenant is rated Low

This tool retrieves and exports tenant data for inspection/backup purposes. It does not modify, delete, or execute arbitrary operations—it simply reads and serializes existing data. The default behavior (without confirm=true) is to return a plan only, further confirming read-only intent. Even when executed, dumping data has no side effects on the database itself.

From the tool's definition Tool name contains 'dump' and description states it 'Dump the configured tenant or a tenant-relative path' and 'returns the mkdir/helper-container plan only' without actual execution by default (unless confirm=true).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

local_ydb_dump_tenant Allowed

local_ydb_dump_tenant is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "local_ydb_dump_tenant": {}
  }
}

ALLOW ONLY 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_dump_tenant call is checked against it from then on.

FAQ

Questions about local_ydb_dump_tenant

What does the local_ydb_dump_tenant tool do? +

How do I enforce a policy on local_ydb_dump_tenant? +

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

local_ydb_dump_tenant is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit local_ydb_dump_tenant? +

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

Set action: deny in the PolicyLayer policy for local_ydb_dump_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_dump_tenant? +

local_ydb_dump_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

Roll out MCP under one policy →Data exfiltration →MCP token cost →