This record as markdown: /tools/io-github-kivanccakmak-yaver/migrate-run.md
What migrate_run does on Yaver
AI agents invoke migrate_run 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 |
|---|---|---|---|
step | integer | — | Specific step number (0 = all remaining) |
plan_id | string | Yes |
Parameters from the server's own tool schema.
Why migrate_run is rated High
This tool runs migration steps which execute database or infrastructure changes. Migrations can be destructive (schema changes, data transformations) and are generally not easily reversible, but since the description doesn't explicitly confirm irreversibility, Execute is the most appropriate category. The blast radius is high as migrations often affect production databases or infrastructure.
From the tool's definition "Execute a migration plan (all steps or a specific step)"
Attacks that exploit this kind of access
The rule that runs migrate_run 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_run, this is the rule to start with:
migrate_run 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 migrate_run call is checked against it from then on.
Questions about migrate_run
Execute a migration plan (all steps or a specific step). 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.
migrate_run accepts 2 parameters: step, plan_id. Required: 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_run: 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_run 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 migrate_run 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_run. 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_run 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