cancel_migration

Cancel a running email migration. Set confirm_cancel=true to proceed.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/cancel-migration.md

WHAT IT DOES

What cancel_migration does on TrekMail MCP Server

AI agents call cancel_migration to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cancel_migration is rated Critical

Cancelling a running migration is an irreversible disruptive action — it aborts an in-progress data migration process that cannot be simply restarted without potential data loss or inconsistency. The confirmation flag ('confirm_cancel=true') signals the irreversible nature of the action.

From the tool's definition Cancel a running email migration. Set confirm_cancel=true to proceed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_migration safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, 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 Hidden

cancel_migration is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_migration"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about cancel_migration

What does the cancel_migration tool do? +

Cancel a running email migration. Set confirm_cancel=true to proceed. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_migration? +

Register the TrekMail MCP Server 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 TrekMail MCP Server. Nothing to install.

What risk level is cancel_migration? +

cancel_migration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_migration? +

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.

How do I block cancel_migration completely? +

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.

What MCP server provides cancel_migration? +

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

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →