digest_run

THE RISK

High Risk

Why digest_run needs a policy

When confirm=true, this tool executes external side-effecting operations by dispatching notifications to Lark and/or Telegram. This qualifies as Execute (triggering external operations), not Destructive in the data-deletion sense.

From the tool's definition 'sends notifications to Lark/Telegram' and 'DESTRUCTIVE if confirm=true' — triggers external operations (outbound notifications to third-party platforms) when confirm=true; defaults to dry-run preview

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

POLICY

How to control digest_run

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Email Service, and nothing reaches the server without passing your rules. This is the rule we recommend for digest_run:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "digest_run": {
      "limits": [
        {
          "counter": "digest_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

digest_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Email Service — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Email Service tools

Destructive email_delete DESTRUCTIVE. Defaults to dry-run; pass confirm=true to delete. By default moves to Trash; Destructive email_flag DESTRUCTIVE. Defaults to dry-run; pass confirm=true to apply. Destructive cleanup Rule-based classifier into protected_finance/protected_travel/security/support_case (never Destructive email_move DESTRUCTIVE. Defaults to dry-run; pass confirm=true to apply. Write email_send DESTRUCTIVE / IRREVERSIBLE. Defaults to dry-run preview; pass confirm=true to actually sen Write sync_force Refresh the local SQLite cache from IMAP. Synchronous; can take 5-30s for first sync. Subs Write email_mark DESTRUCTIVE. Defaults to dry-run; pass confirm=true to actually flip flags. Read account_list Returns every account known to mailbox: id, email, provider (gmail/qq/163/outlook/...), IM

All 16 MCP Email Service tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MCP Email Service → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about digest_run

What does the digest_run tool do? +

DESTRUCTIVE if confirm=true (sends notifications to Lark/Telegram). Defaults to dry-run preview. It is categorised as a Execute tool in the MCP Email Service MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on digest_run? +

Register the MCP Email Service MCP server in PolicyLayer and add a rule for digest_run: 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 MCP Email Service. Nothing to install.

What risk level is digest_run? +

digest_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit digest_run? +

Yes. Add a rate_limit block to the digest_run 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 digest_run completely? +

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

digest_run is provided by the MCP Email Service MCP server (leeguooooo/mailbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Email Service tool call.

Start from MCP Email Service, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →