This record as markdown: /tools/io-github-devopam-mcpg/cancel-migration.md
What cancel_migration does on Mcpg
AI agents call cancel_migration to permanently remove resources in Mcpg, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_migration is rated Critical
Cancelling a migration could irreversibly halt a data migration operation, potentially leaving data in an inconsistent or partial state. Given the PostgreSQL context and the destructive potential of interrupting migrations, this warrants a Destructive classification. However, confidence is low due to the empty description — it could alternatively be a Write or Execute action if the migration can be safely resumed.
From the tool's definition Tool name 'cancel_migration' suggests terminating a migration process; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs cancel_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 cancel_migration, this is the rule to start with:
cancel_migration is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every cancel_migration call is checked against it from then on.
Questions about cancel_migration
cancel_migration is a destructive tool on the Mcpg MCP server. It is categorised as a Destructive tool in the Mcpg MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcpg MCP server in PolicyLayer and add a rule for cancel_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.
cancel_migration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_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 cancel_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.
cancel_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.
Across the catalogue