This record as markdown: /tools/io-github-devopam-mcpg/validate-migration.md
What validate_migration does on Mcpg
AI agents invoke validate_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 validate_migration is rated High
The name 'validate_migration' suggests running a validation process against a database migration, which typically involves executing queries or checks against the database schema/data. In a PostgreSQL MCP context, this likely triggers some form of execution to verify migration state. However, since the description is empty, confidence is reduced. It could also be a Read operation (just querying migration status).
From the tool's definition Tool name: 'validate_migration'; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs validate_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 validate_migration, this is the rule to start with:
validate_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 validate_migration call is checked against it from then on.
Questions about validate_migration
validate_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 validate_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.
validate_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 validate_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 validate_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.
validate_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