retry_bulk_migration
Retry all failed jobs in a bulk migration batch. Requires TREKMAIL_ALLOW_MIGRATION=true and confirm_retry=true.
This record as markdown: /tools/trekmail-mcp-server/retry-bulk-migration.md
What retry_bulk_migration does on TrekMail MCP Server
AI agents invoke retry_bulk_migration to trigger actions in TrekMail MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why retry_bulk_migration is rated High
Retrying a bulk migration re-executes potentially large-scale data movement operations across many mailboxes. While not purely destructive (it's retrying failed jobs rather than deleting), it is an external operation with broad blast radius — misconfigured or mistargeted retries could cause data duplication, overwrites, or service disruption at scale.
From the tool's definition 'Retry all failed jobs in a bulk migration batch' — triggers re-execution of migration jobs; requires confirm_retry=true gate indicating significant operational impact
Attacks that exploit this kind of access
The rule that runs retry_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 retry_bulk_migration, this is the rule to start with:
retry_bulk_migration stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every retry_bulk_migration call is checked against it from then on.
Questions about retry_bulk_migration
Retry all failed jobs in a bulk migration batch. Requires TREKMAIL_ALLOW_MIGRATION=true and confirm_retry=true. It is categorised as a Execute tool in the TrekMail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for retry_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.
retry_bulk_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the retry_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 retry_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.
retry_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