// MCP TOOL REFERENCE

local_ydb_permissions

List, grant, revoke, set, clear, chown, or toggle inheritance for YDB scheme permissions.

Accepts file system path (path)

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

// WHEN AI AGENTS USE THIS TOOL

AI agents may call local_ydb_permissions 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.

// WHY ENFORCE A POLICY ON LOCAL_YDB_PERMISSIONS

Without a policy, an AI agent could call local_ydb_permissions 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.

// RECOMMENDED POLICY

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

local-ydb.yaml

tools:
  local_ydb_permissions:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Local Ydb policy for all 34 tools.

// DETAILS

Tool Name local_ydb_permissions

Category Destructive

MCP Server Local Ydb MCP Server

Risk Level Critical

// MORE LOCAL YDB TOOLS

Destructive local_ydb_cleanup_storage Destructive local_ydb_destroy_stack Destructive local_ydb_remove_dynamic_nodes Execute local_ydb_pull_image Execute local_ydb_restart_stack Execute local_ydb_start_dynamic_node Write local_ydb_add_dynamic_nodes Write local_ydb_add_storage_groups

View all 34 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

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

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete ACR — Agent Composition Records acknowledge_signal AdButler campaign_bulk_delete_catalog_ad_items

// IN CONTEXT OF CRITICAL RISK

local_ydb_permissions 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.

// RELATED READING

// FAQ

What does the local_ydb_permissions tool do? +

List, grant, revoke, set, clear, chown, or toggle inheritance for YDB scheme permissions.. 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_permissions? +

Add a rule in your Intercept YAML policy under the tools section for local_ydb_permissions. 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_permissions? +

local_ydb_permissions 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_permissions? +

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

Set action: deny in the Intercept policy for local_ydb_permissions. 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_permissions? +

local_ydb_permissions 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.

local_ydb_permissions

Let agents act without letting them run wild.