cli_migration_run · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_migration_run does on LaunchFrame MCP

AI agents invoke cli_migration_run to trigger actions in LaunchFrame MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why cli_migration_run needs a policy

The tool executes database migrations, which are code-driven schema/data modifications. While migrations are typically reversible through rollback, the immediate action is execution of arbitrary database operations whose side effects depend on the pending migrations in the codebase.

From the tool's definition Tool name contains 'run' and description states 'Run all pending TypeORM database migrations against the local database' - explicitly indicates execution of database migration operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_migration_run Rate-limited

cli_migration_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cli_migration_run": {
      "limits": [
        {
          "counter": "cli_migration_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about cli_migration_run

What does the cli_migration_run tool do? +

Run all pending TypeORM database migrations against the local database. It is categorised as a Execute tool in the LaunchFrame MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cli_migration_run? +

Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_migration_run: 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 LaunchFrame MCP. Nothing to install.

What risk level is cli_migration_run? +

cli_migration_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cli_migration_run? +

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

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

cli_migration_run is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.