complete_migration

A execute tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/complete-migration.md

WHAT IT DOES

What complete_migration does on Mcpg

AI agents invoke complete_migration to trigger actions in Mcpg. 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.

RISK

Why complete_migration is rated High

The name 'complete_migration' strongly implies finalizing a database migration, which typically involves executing schema or data changes that may be partially or fully irreversible. On a production PostgreSQL server, this could include DDL changes, data transformations, or cleanup of migration state.

From the tool's definition Tool name 'complete_migration' on a production-grade PostgreSQL MCP server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs complete_migration safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For complete_migration, this is the rule to start with:

complete_migration Rate-limited

complete_migration 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": {
    "complete_migration": {
      "limits": [
        {
          "counter": "complete_migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every complete_migration call is checked against it from then on.

FAQ

Questions about complete_migration

What does the complete_migration tool do? +

complete_migration is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on complete_migration? +

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

What risk level is complete_migration? +

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

Can I rate-limit complete_migration? +

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

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

complete_migration is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →