AI agents use bulk_mark_read 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.
This tool modifies email metadata (read/unread flags) but does not delete, create new messages, or execute arbitrary operations. Changes are reversible—emails can be marked unread again. While it affects message state, the blast radius is moderate since it only toggles metadata flags without data loss or external side effects.
From the tool's definition Tool description states 'Mark multiple emails as read/unread' — this modifies the read/unread state of existing emails, which is a reversible change to email metadata. The 'bulk_' prefix indicates it operates on multiple messages at once.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_mark_read 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 bulk_mark_read:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_mark_read": {
"limits": [
{
"counter": "bulk_mark_read_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} bulk_mark_read 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.
Mark multiple emails as 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 bulk_mark_read: 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.
bulk_mark_read 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 bulk_mark_read 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_mark_read. 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_mark_read 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.