Low Risk

list_recent_bulk_ops

List recent bulk_modify and bulk_trash operations recorded in the transaction log. Use to find an op id for undo_bulk_op.

Part of the Mailbox MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call list_recent_bulk_ops to retrieve information from Mailbox without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_recent_bulk_ops only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

mailbox.yaml
tools:
  list_recent_bulk_ops:
    rules:
      - action: allow

See the full Mailbox policy for all 49 tools.

Tool Name list_recent_bulk_ops
Category Read
MCP Server Mailbox MCP Server
Risk Level Low

View all 49 tools →

Agents calling read-class tools like list_recent_bulk_ops have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the list_recent_bulk_ops tool do? +

List recent bulk_modify and bulk_trash operations recorded in the transaction log. Use to find an op id for undo_bulk_op.. It is categorised as a Read tool in the Mailbox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recent_bulk_ops? +

Add a rule in your Intercept YAML policy under the tools section for list_recent_bulk_ops. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mailbox MCP server.

What risk level is list_recent_bulk_ops? +

list_recent_bulk_ops is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_recent_bulk_ops? +

Yes. Add a rate_limit block to the list_recent_bulk_ops rule in your Intercept 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 list_recent_bulk_ops completely? +

Set action: deny in the Intercept policy for list_recent_bulk_ops. 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 list_recent_bulk_ops? +

list_recent_bulk_ops is provided by the Mailbox MCP server (mailbox-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.