db_migrate
Run pending database migrations. Auto-detects ORM (Drizzle, Prisma, Goose, Alembic).
This record as markdown: /tools/io-github-kivanccakmak-yaver/db-migrate.md
What db_migrate does on Yaver
AI agents invoke db_migrate to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
target | string | — | Target: local or production (default: local) |
Parameters from the server's own tool schema.
Why db_migrate is rated High
Running database migrations executes schema-altering operations (CREATE TABLE, ALTER TABLE, potentially DROP TABLE) that modify the database structure. While some migrations are reversible, many are not (e.g., dropping columns, data transformations), and the tool itself is an execution trigger rather than a pure write or destructive action.
From the tool's definition 'Run pending database migrations' — executes migration scripts against a live database, auto-detecting and invoking ORM tooling (Drizzle, Prisma, Goose, Alembic).
Attacks that exploit this kind of access
The rule that runs db_migrate 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_migrate, this is the rule to start with:
db_migrate stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_migrate call is checked against it from then on.
Questions about db_migrate
Run pending database migrations. Auto-detects ORM (Drizzle, Prisma, Goose, Alembic). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
db_migrate accepts 1 parameter: target. 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_migrate: 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_migrate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the db_migrate 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_migrate. 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_migrate 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.
Across the catalogue