bulk_action
Perform an action on up to 50 messages at once. Actions: read, unread, star, unstar, delete, move, spam, notspam. The
This record as markdown: /tools/trekmail-mcp-server/bulk-action.md
What bulk_action does on TrekMail MCP Server
AI agents call bulk_action 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 bulk_action is rated Critical
While the tool offers multiple actions (read, unread, star, unstar, move, spam, notspam) that would typically be Write or Execute category, the inclusion of 'delete' as a supported action elevates this to Destructive. Deleting messages is irreversible and cannot be undone. The ability to delete up to 50 messages in a single operation increases the blast radius.
From the tool's definition Tool description explicitly lists 'delete' as one of the bulk actions it can perform on up to 50 messages at once. This is irreversible data removal.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_action 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 bulk_action, this is the rule to start with:
bulk_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every bulk_action call is checked against it from then on.
Questions about bulk_action
Perform an action on up to 50 messages at once. Actions: read, unread, star, unstar, delete, move, spam, notspam. The. 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.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for bulk_action: 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.
bulk_action is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bulk_action 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 bulk_action. 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.
bulk_action 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