cancel_bulk_migration

Cancel an active bulk migration batch. All queued and running jobs will be stopped. Set confirm_cancel=true to proceed.

Server TrekMail MCP Server trekmail/mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

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 needs a policy

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.

Questions about cancel_bulk_migration

What does the cancel_bulk_migration tool do? +

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.

How do I enforce a policy on cancel_bulk_migration? +

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.

What risk level is cancel_bulk_migration? +

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.

Can I rate-limit cancel_bulk_migration? +

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.

How do I block cancel_bulk_migration completely? +

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.

What MCP server provides cancel_bulk_migration? +

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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.