generate_migration_plan

THE RISK

Medium Risk

Why generate_migration_plan needs a policy

This tool writes (creates) a migration plan document/artifact, modifying the state of planning/configuration data. While it doesn't directly execute migrations or delete data, it produces executable instructions that could significantly alter authentication infrastructure if followed.

From the tool's definition Tool creates a 'step-by-step migration plan' which constitutes generating and storing new configuration/documentation artifacts. The verb 'generate' with 'migration plan' indicates creation of structured data that will guide authentication system changes.

Documented attack patterns abuse exactly the kind of access generate_migration_plan gives an agent:

POLICY

How to control generate_migration_plan

PolicyLayer is an MCP gateway — it sits between your AI agents and Better Auth MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_migration_plan:

policy.json

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

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

Create a free account and register Better Auth MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Better Auth MCP Server tools

Execute test_auth_flows Test authentication workflows Execute test_security Run security tests on Better-Auth setup Write setup_better_auth Install and configure Better-Auth in the project Read analyze_current_auth Detect and analyze existing auth.js/next-auth implementation Read analyze_logs Analyze Better-Auth logs for issues Read analyze_project Analyze project structure and dependencies to recommend Better-Auth setup approach Read monitor_auth_flows Real-time monitoring of authentication processes

All 8 Better Auth MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about generate_migration_plan

What does the generate_migration_plan tool do? +

Create step-by-step migration plan from existing auth to Better-Auth. It is categorised as a Write tool in the Better Auth MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_migration_plan? +

Register the Better Auth MCP Server MCP server in PolicyLayer and add a rule for generate_migration_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 Better Auth MCP Server. Nothing to install.

What risk level is generate_migration_plan? +

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

Can I rate-limit generate_migration_plan? +

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

Set action: deny in the PolicyLayer policy for generate_migration_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 generate_migration_plan? +

generate_migration_plan is provided by the Better Auth MCP Server MCP server (jamesjohnsdev/better-auth-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Better Auth MCP Server tool call.

Start from Better Auth MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →