List bulk migration batches for your account. Supports filtering by status.
AI agents call list_bulk_migrations 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 queries and lists existing bulk migration records, filtered by status. It retrieves data without creating, modifying, deleting, or executing any operations. The 'list' verb is characteristic of Read category tools. No destructive or financial impact is possible from simply viewing migration batch information.
From the tool's definition Tool name 'list_bulk_migrations' and description 'List bulk migration batches for your account. Supports filtering by status.' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List bulk migration batches for your account. Supports filtering by status. 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 list_bulk_migrations: 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.
list_bulk_migrations 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 list_bulk_migrations 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 list_bulk_migrations. 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.
list_bulk_migrations 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 →