get_migration_path
Prescriptive migration plan between DIFFERENT packages — rationale + literal code diff + breaking changes + effort minutes. USE WHEN: replacing request→axios, moment→dayjs, flask→fastapi, etc.; both endpoints known. RETURNS: {rationale, diff, breaking_changes[], estimated_minutes}.
This record as markdown: /tools/dev-depscope-mcp/get-migration-path.md
What get_migration_path does on Depscope
AI agents call get_migration_path to retrieve information from Depscope without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ecosystem | string | Yes | |
to_package | string | Yes | Modern replacement package. |
from_package | string | Yes | Deprecated/legacy package to migrate away from. |
Parameters from the server's own tool schema.
Why get_migration_path is rated Low
get_migration_path retrieves and presents analysis data about how to migrate between packages. It reads package metadata and generates a migration recommendation with code diffs and effort estimates. No side effects, no data modification, no code execution—purely informational/advisory output.
From the tool's definition Tool description explicitly states it RETURNS data: {rationale, diff, breaking_changes[], estimated_minutes}. No mutations, deletions, or external code execution mentioned. It 'prescribes' a migration plan (advisory/informational), not executes one.
Attacks that exploit this kind of access
The rule that runs get_migration_path safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_migration_path, this is the rule to start with:
get_migration_path is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Depscope, apply this rule, and every get_migration_path call is checked against it from then on.
Questions about get_migration_path
Prescriptive migration plan between DIFFERENT packages — rationale + literal code diff + breaking changes + effort minutes. USE WHEN: replacing request→axios, moment→dayjs, flask→fastapi, etc.; both endpoints known. RETURNS: {rationale, diff, breaking_changes[], estimated_minutes}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_migration_path accepts 3 parameters: ecosystem, to_package, from_package. Required: ecosystem, to_package, from_package. The full parameter table on this page comes from the server's own tool schema.
Register the Depscope MCP server in PolicyLayer and add a rule for get_migration_path: 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 Depscope. Nothing to install.
get_migration_path is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_migration_path 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 get_migration_path. 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.
get_migration_path is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Depscope, and thousands of servers like it.
This server
Across the catalogue