Critical Risk →

bulk_delete

Delete multiple emails (move to trash)

How to control bulk_delete ↓

What bulk_delete does on Fastmail MCP Server

AI agents call bulk_delete to permanently remove resources in Fastmail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why bulk_delete needs a policy

Although technically moved to trash rather than permanently purged, this tool irreversibly removes emails from normal access and organization. An AI agent with misuse could delete large volumes of user emails, causing significant data loss. This exceeds Write (which is reversible) and qualifies as Destructive.

From the tool's definition Tool name 'bulk_delete' combined with description 'Delete multiple emails (move to trash)' indicates irreversible removal of data. The word 'delete' is explicit, and moving to trash is a destructive action that removes emails from the user's active mailbox.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access bulk_delete gives an agent:

How to control bulk_delete

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_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "bulk_delete"
  ]
}

bulk_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Fastmail MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about bulk_delete

What does the bulk_delete tool do? +

Delete multiple emails (move to trash). It is categorised as a Destructive tool in the Fastmail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on bulk_delete? +

Register the Fastmail MCP Server MCP server in PolicyLayer and add a rule for bulk_delete: 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.

What risk level is bulk_delete? +

bulk_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bulk_delete? +

Yes. Add a rate_limit block to the bulk_delete 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.

How do I block bulk_delete completely? +

Set action: deny in the PolicyLayer policy for bulk_delete. 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.

What MCP server provides bulk_delete? +

bulk_delete 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.

Enforce policy on every Fastmail MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.