This record as markdown: /tools/io-github-kivanccakmak-yaver/prisma-push.md
What prisma_push does on Yaver
AI agents invoke prisma_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 prisma_push is rated High
'prisma db push' is a CLI command execution that pushes schema changes to the database without migrations, potentially altering or destroying existing data structures. It can drop columns/tables if the schema removes them, making it borderline Destructive, but its primary nature is executing an external command. Severity is high because misuse could cause irreversible data loss in a database.
From the tool's definition 'Run prisma db push' — executes Prisma's db 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 prisma_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 prisma_push, this is the rule to start with:
prisma_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 prisma_push call is checked against it from then on.
Questions about prisma_push
Run prisma db 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.
prisma_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 prisma_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.
prisma_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 prisma_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 prisma_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.
prisma_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