cancel_bulk_migration
Cancel an active bulk migration batch. All queued and running jobs will be stopped. Set confirm_cancel=true to proceed.
This record as markdown: /tools/trekmail-mcp-server/cancel-bulk-migration.md
What cancel_bulk_migration does on TrekMail MCP Server
AI agents call cancel_bulk_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.
Why cancel_bulk_migration is rated Critical
Cancelling a bulk migration batch irreversibly stops all queued and running migration jobs. While it may not delete data outright, stopping an in-progress migration can leave data in an inconsistent or partially migrated state that is difficult or impossible to recover, making this effectively irreversible. The 'confirm_cancel=true' requirement signals the action is significant and non-trivial to undo.
From the tool's definition Cancel an active bulk migration batch. All queued and running jobs will be stopped.
Attacks that exploit this kind of access
The rule that runs cancel_bulk_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_bulk_migration, this is the rule to start with:
cancel_bulk_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 TrekMail MCP Server, apply this rule, and every cancel_bulk_migration call is checked against it from then on.
Questions about cancel_bulk_migration
Cancel an active bulk migration batch. All queued and running jobs will be stopped. 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.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for cancel_bulk_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.
cancel_bulk_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_bulk_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_bulk_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_bulk_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.
More on TrekMail MCP Server, and thousands of servers like it.
Across the catalogue