Get details of a bulk migration batch including per-job status breakdown.
AI agents call get_bulk_migration to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries status information about bulk migration batches. It has no side effects—it does not create, modify, delete, or execute operations. It falls squarely into the Read category as a data retrieval operation. Severity is low because viewing migration status poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_bulk_migration' uses the 'get' verb and description states 'Get details' with 'per-job status breakdown', indicating retrieval of existing migration batch information with no modification or deletion of data.
Attacks that exploit this kind of access
Get details of a bulk migration batch including per-job status breakdown. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_bulk_migration is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.
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 →