db_apply_all_migrations · Database MCP Server MCP

WHAT IT DOES

What db_apply_all_migrations does on Database MCP Server

AI agents invoke db_apply_all_migrations to trigger actions in Database MCP Server. 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 db_apply_all_migrations needs a policy

Applying database migrations executes DDL/DML changes against the database schema and data. While some migrations are reversible, migrations as a whole can include destructive operations (DROP, ALTER, DELETE), making this an Execute-category action with high severity. The tool runs multiple migrations in sequence, amplifying blast radius if any migration contains irreversible changes.

From the tool's definition 'Apply all pending migrations to sync the database. Runs migrations in order.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db_apply_all_migrations Rate-limited

db_apply_all_migrations 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": {
    "db_apply_all_migrations": {
      "limits": [
        {
          "counter": "db_apply_all_migrations_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 Database MCP Server, so you can run agents against it safely.

FAQ

Questions about db_apply_all_migrations

What does the db_apply_all_migrations tool do? +

Apply all pending migrations to sync the database. Runs migrations in order. It is categorised as a Execute tool in the Database MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on db_apply_all_migrations? +

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

What risk level is db_apply_all_migrations? +

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

Can I rate-limit db_apply_all_migrations? +

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

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

db_apply_all_migrations is provided by the Database MCP Server MCP server (roilanrodriguez55/database-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.