New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

db_generate

Generate a new migration from schema changes.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 10 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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

Questions about db_generate

What does the db_generate tool do? +

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.

What parameters does db_generate accept? +

db_generate accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on db_generate? +

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.

What risk level is db_generate? +

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

Can I rate-limit db_generate? +

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.

How do I block db_generate completely? +

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.

What MCP server provides db_generate? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.