cli_migration_create · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cli_migration_create does on LaunchFrame MCP

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

WHY IT NEEDS A POLICY

Why cli_migration_create needs a policy

This tool creates new migration files, which are reversible modifications to the codebase. While migrations can eventually lead to destructive database operations when executed, the tool itself only generates an empty migration file template - it does not execute migrations or delete data. The Write category is appropriate because it creates a new artifact.

From the tool's definition Tool description states 'Create a new empty TypeORM migration file' - the verb 'Create' indicates data creation. TypeORM migration files are code artifacts that modify database schema.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cli_migration_create Rate-limited

cli_migration_create 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": {
    "cli_migration_create": {
      "limits": [
        {
          "counter": "cli_migration_create_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 LaunchFrame MCP, so you can run agents against it safely.

FAQ

Questions about cli_migration_create

What does the cli_migration_create tool do? +

Create a new empty TypeORM migration file with the given name. It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cli_migration_create? +

Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_migration_create: 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_create? +

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

Can I rate-limit cli_migration_create? +

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

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

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