This record as markdown: /tools/io-github-kivanccakmak-yaver/migrate-rollback.md
What migrate_rollback does on Yaver
AI agents call migrate_rollback 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
step | integer | Yes | |
plan_id | string | Yes |
Parameters from the server's own tool schema.
Why migrate_rollback is rated Critical
Database migration rollbacks undo applied migrations, which can drop tables, columns, or data that was created by the migration. This is effectively irreversible in most cases, especially if data was inserted after the migration was applied. The blast radius is high as it can affect the entire database schema and any dependent data.
From the tool's definition 'migrate_rollback' and 'Rollback a migration step' — rolling back a migration reverses schema or data changes, which can be irreversible (data loss, schema destruction).
Attacks that exploit this kind of access
The rule that runs migrate_rollback 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 migrate_rollback, this is the rule to start with:
migrate_rollback 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 migrate_rollback call is checked against it from then on.
Questions about migrate_rollback
Rollback a migration step. 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.
migrate_rollback accepts 2 parameters: step, plan_id. Required: step, plan_id. 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 migrate_rollback: 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.
migrate_rollback 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 migrate_rollback 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 migrate_rollback. 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.
migrate_rollback 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