Test bulk operations by finding recent emails and performing safe operations (mark read/unread)
AI agents use test_bulk_operations to create or update resources in Fastmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fastmail MCP Server environment.
The tool performs bulk write operations (marking emails as read/unread) across multiple messages. While described as 'safe' and reversible, it can modify the state of many emails at once, making it a Write category with medium severity due to the bulk nature of the changes.
From the tool's definition 'performing safe operations (mark read/unread)' — modifies email read state across potentially many emails
Documented attack patterns abuse exactly the kind of access test_bulk_operations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fastmail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_bulk_operations:
{
"version": "1",
"default": "deny",
"tools": {
"test_bulk_operations": {
"limits": [
{
"counter": "test_bulk_operations_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} test_bulk_operations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test bulk operations by finding recent emails and performing safe operations (mark read/unread). It is categorised as a Write tool in the Fastmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fastmail MCP Server MCP server in PolicyLayer and add a rule for test_bulk_operations: 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 Fastmail MCP Server. Nothing to install.
test_bulk_operations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the test_bulk_operations 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 test_bulk_operations. 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.
test_bulk_operations is provided by the Fastmail MCP Server MCP server (madllama25/fastmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fastmail MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 Fastmail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.