This record as markdown: /tools/io-github-kivanccakmak-yaver/db-generate.md
What db_generate does on Yaver
AI agents use db_generate to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Migration name |
Parameters from the server's own tool schema.
Why db_generate is rated Medium
This tool creates new migration files based on schema changes, which modifies the codebase and database structure. While migrations are designed to be reversible (unlike destructive operations), they represent write operations that alter system state. The tool does not delete data irreversibly, execute arbitrary code, or move money, but it does create new database artifacts that modify infrastructure.
From the tool's definition Tool name 'db_generate' and description 'Generate a new migration from schema changes' indicate creation of database migration artifacts. Migrations are reversible modifications to database schemas.
Attacks that exploit this kind of access
The rule that runs db_generate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For db_generate, this is the rule to start with:
db_generate 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every db_generate call is checked against it from then on.
Questions about db_generate
Generate a new migration from schema changes. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
db_generate accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for db_generate: 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 Yaver. Nothing to install.
db_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the db_generate 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 db_generate. 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.
db_generate is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue