db_push
Push schema directly to database (dev only, skips migration files).
This record as markdown: /tools/io-github-kivanccakmak-yaver/db-push.md
What db_push does on Yaver
AI agents call db_push to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why db_push is rated Critical
Pushing a schema directly to a database, especially while skipping migration files, can result in destructive operations such as dropping columns, tables, or constraints that cannot be undone. The absence of migration files means there is no reversible audit trail or rollback mechanism, making this effectively irreversible.
From the tool's definition 'Push schema directly to database' and 'skips migration files' — directly applying schema changes without migration history can overwrite, drop, or alter tables irreversibly with no rollback path.
Attacks that exploit this kind of access
The rule that runs db_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 db_push, this is the rule to start with:
db_push is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every db_push call is checked against it from then on.
Questions about db_push
Push schema directly to database (dev only, skips migration files). It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Yaver MCP server in PolicyLayer and add a rule for db_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.
db_push is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the db_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 db_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.
db_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