This record as markdown: /tools/io-github-kivanccakmak-yaver/drizzle-push.md
What drizzle_push does on Yaver
AI agents invoke drizzle_push 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why drizzle_push is rated High
drizzle-kit push is a CLI command that pushes schema changes directly to a live database, bypassing migration files. This is an execution of an external tool with potentially destructive side effects (schema alterations, column drops) depending on the schema diff.
From the tool's definition 'Run drizzle-kit push' — executes the drizzle-kit push command which applies schema changes directly to the database
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs drizzle_push 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 drizzle_push, this is the rule to start with:
drizzle_push 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 drizzle_push call is checked against it from then on.
Questions about drizzle_push
Run drizzle-kit push. 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.
drizzle_push accepts 1 parameter: directory. 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 drizzle_push: 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.
drizzle_push 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 drizzle_push 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 drizzle_push. 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.
drizzle_push 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