This record as markdown: /tools/io-github-devopam-mcpg/prepare-migration.md
What prepare_migration does on Mcpg
AI agents invoke prepare_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.
Why prepare_migration is rated High
Database migrations typically involve executing schema changes (ALTER TABLE, CREATE TABLE, etc.) against a PostgreSQL database. 'Prepare' suggests it may stage or initiate a migration process, which is an Execute-level action. However, it could also be Destructive if it drops/alters columns irreversibly, or Write if it only stages metadata. Given the empty description, confidence is low.
From the tool's definition Tool name 'prepare_migration' on a production-grade PostgreSQL MCP server. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs prepare_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 prepare_migration, this is the rule to start with:
prepare_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every prepare_migration call is checked against it from then on.
Questions about prepare_migration
prepare_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.
Register the Mcpg MCP server in PolicyLayer and add a rule for prepare_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.
prepare_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prepare_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.
Set action: deny in the PolicyLayer policy for prepare_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.
prepare_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.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue