This record as markdown: /tools/io-github-kivanccakmak-yaver/drizzle-generate.md
What drizzle_generate does on Yaver
AI agents invoke drizzle_generate 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_generate is rated High
The tool executes an external build/codegen process (drizzle-kit generate). While it primarily generates files (a Write-like outcome), the act of running an external CLI command places it in the Execute category. Misuse could generate incorrect migrations or overwrite schema files, but effects are generally reversible, warranting medium severity.
From the tool's definition "Run drizzle-kit generate" — explicitly runs an external CLI tool (drizzle-kit generate) to produce migration files or schema artifacts
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs drizzle_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 drizzle_generate, this is the rule to start with:
drizzle_generate 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_generate call is checked against it from then on.
Questions about drizzle_generate
Run drizzle-kit generate. 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_generate 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_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.
drizzle_generate 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_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 drizzle_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.
drizzle_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.
Across the catalogue