delete_migration

Delete a completed, failed, or cancelled migration record. Cannot delete running migrations. Both TREKMAIL_ALLOW_MIGRATION=true and confirm_delete=true are required.

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

What delete_migration does on TrekMail MCP Server

AI agents call delete_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 delete_migration needs a policy

This tool irreversibly deletes migration records from the system. Although it cannot delete running migrations, it removes completed, failed, or cancelled migrations that cannot be recovered. Deletion is the primary destructive operation. The high severity reflects that migration records may be critical for compliance, auditing, and recovery workflows.

From the tool's definition "Delete a completed, failed, or cancelled migration record" - the tool permanently removes migration records with no undo mechanism. Requires explicit confirmation (confirm_delete=true), indicating irreversible action.

Questions about delete_migration

What does the delete_migration tool do? +

Delete a completed, failed, or cancelled migration record. Cannot delete running migrations. Both TREKMAIL_ALLOW_MIGRATION=true and confirm_delete=true are required. 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 delete_migration? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for delete_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 delete_migration? +

delete_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 delete_migration? +

Yes. Add a rate_limit block to the delete_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 delete_migration completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_migration? +

delete_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.