migrate_targets

List all supported migration targets with pros, cons, and costs.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/migrate-targets.md

WHAT IT DOES

What migrate_targets does on Yaver

AI agents call migrate_targets to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why migrate_targets is rated Low

The tool only lists migration targets along with their attributes (pros, cons, costs). This is a read-only informational query with no modifications, executions, or destructive actions.

From the tool's definition 'List all supported migration targets with pros, cons, and costs' — purely retrieves and presents informational data with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs migrate_targets 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_targets, this is the rule to start with:

migrate_targets Allowed

migrate_targets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "migrate_targets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every migrate_targets call is checked against it from then on.

FAQ

Questions about migrate_targets

What does the migrate_targets tool do? +

List all supported migration targets with pros, cons, and costs. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on migrate_targets? +

Register the Yaver MCP server in PolicyLayer and add a rule for migrate_targets: 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_targets? +

migrate_targets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit migrate_targets? +

Yes. Add a rate_limit block to the migrate_targets 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_targets completely? +

Set action: deny in the PolicyLayer policy for migrate_targets. 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_targets? +

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →