migrate_verify
Run smoke tests after migration to verify everything works.
This record as markdown: /tools/io-github-kivanccakmak-yaver/migrate-verify.md
What migrate_verify does on Yaver
AI agents invoke migrate_verify 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 |
|---|---|---|---|
plan_id | string | Yes |
Parameters from the server's own tool schema.
Why migrate_verify is rated High
The tool executes smoke tests, which involves running code and triggering external operations to verify system state. While it is primarily a verification/read action, it actively executes test routines rather than passively querying data. The blast radius is medium since misuse could trigger unintended side effects during post-migration testing, though it is not inherently destructive.
From the tool's definition 'Run smoke tests after migration to verify everything works' — actively runs tests/operations post-migration
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs migrate_verify 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_verify, this is the rule to start with:
migrate_verify 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_verify call is checked against it from then on.
Questions about migrate_verify
Run smoke tests after migration to verify everything works. 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_verify accepts 1 parameter: 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_verify: 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_verify 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_verify 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_verify. 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_verify 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