generate_migration_plan · Better Auth MCP Server MCP

WHAT IT DOES

What generate_migration_plan does on Better Auth MCP Server

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

WHY IT NEEDS A POLICY

Why generate_migration_plan needs a policy

This tool generates and creates plan documentation, which constitutes data creation (Write category). While migration plans guide subsequent actions, the tool itself only creates the plan artifact without executing the actual migration or making irreversible changes to the auth system.

From the tool's definition The tool 'generate_migration_plan' creates a step-by-step migration plan. The verb 'generate' and 'create' indicates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_migration_plan Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_migration_plan": {
      "limits": [
        {
          "counter": "generate_migration_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 Better Auth MCP Server, so you can run agents against it safely.

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 (lexiconalex/better-auth-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.