local_ydb_generate_schema
Read-only structured YDB table DDL generator. It renders strict JSON specs for CREATE TABLE, ALTER TABLE, DROP TABLE, and secondary indexes, returns the generated script with official references and warnings, and can optionally validate through the YDB JS SDK without applying changes.
This record as markdown: /tools/local-ydb/local-ydb-generate-schema.md
What local_ydb_generate_schema does on Local Ydb
AI agents call local_ydb_generate_schema 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.
Why local_ydb_generate_schema is rated Low
The tool only generates and optionally validates DDL scripts (CREATE TABLE, ALTER TABLE, DROP TABLE) but explicitly does not apply any changes. It is purely a read/generation operation with no side effects on the database. The mention of DROP TABLE in the output is concerning but since nothing is executed, the category remains Read.
From the tool's definition Read-only structured YDB table DDL generator... returns the generated script... without applying changes
Attacks that exploit this kind of access
The rule that runs local_ydb_generate_schema 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_generate_schema, this is the rule to start with:
local_ydb_generate_schema is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local Ydb, apply this rule, and every local_ydb_generate_schema call is checked against it from then on.
Questions about local_ydb_generate_schema
Read-only structured YDB table DDL generator. It renders strict JSON specs for CREATE TABLE, ALTER TABLE, DROP TABLE, and secondary indexes, returns the generated script with official references and warnings, and can optionally validate through the YDB JS SDK without applying changes. It is categorised as a Read tool in the Local Ydb MCP Server, which means it retrieves data without modifying state.
Register the Local Ydb MCP server in PolicyLayer and add a rule for local_ydb_generate_schema: 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_generate_schema is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the local_ydb_generate_schema 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_generate_schema. 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_generate_schema 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.
This server
Across the catalogue