migrate_plan · Yaver MCP: Risk & Policy

WHAT IT DOES

What migrate_plan does on Yaver

AI agents use migrate_plan to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

PARAMETERS

Parameter	Type	Required	Description
`to`	string	Yes	Target tier
`from`	string	—	Source tier (auto-detected if omitted)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why migrate_plan needs a policy

An AI agent can call migrate_plan faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_plan Rate-limited

migrate_plan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "migrate_plan": {
      "limits": [
        {
          "counter": "migrate_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about migrate_plan

What does the migrate_plan tool do? +

Generate a migration plan between tiers (local, self-hosted, yaver-cloud, vercel, fly, cloudflare, railway). It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does migrate_plan accept? +

migrate_plan accepts 2 parameters: to, from. Required: to. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on migrate_plan? +

Register the Yaver MCP server in PolicyLayer and add a rule for migrate_plan: 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.

What risk level is migrate_plan? +

migrate_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit migrate_plan? +

Yes. Add a rate_limit block to the migrate_plan 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.

How do I block migrate_plan completely? +

Set action: deny in the PolicyLayer policy for migrate_plan. 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.

What MCP server provides migrate_plan? +

migrate_plan 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.