delete_emails

THE RISK

Critical Risk

Why delete_emails needs a policy

This tool deletes user data (emails) from their mailbox. While technically recoverable from Trash, deletion is operationally irreversible for normal users and represents data loss. The impact on user data and the inability to undo the action within normal operations classifies this as Destructive rather than Write. An AI agent with access could permanently lose important emails.

From the tool's definition Tool description states 'Move emails to Trash folder' and server description includes 'deleting emails'. Although characterized as 'soft delete, recoverable', the tool irreversibly removes emails from the user's active mailbox and normal workflow, which is…

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

POLICY

How to control delete_emails

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_emails"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Yahoo Mail tools

Write unflag_emails Remove flag/star from emails using UIDs. UIDs are permanent identifiers. Write flag_emails Flag emails as important/starred using UIDs. UIDs are permanent identifiers. Write archive_emails Move emails to Archive folder using UIDs for long-term storage. UIDs are permanent identif Write mark_as_read Mark emails as read using UIDs. UIDs are permanent identifiers. Write mark_as_unread Mark emails as unread using UIDs. UIDs are permanent identifiers. Write move_emails Move emails to a specified folder using UIDs. UIDs are permanent identifiers. Use list_fol Read list_emails List recent emails from a Yahoo Mail folder. Returns UIDs (permanent identifiers) and enri Read list_folders List all available IMAP folders/mailboxes in your Yahoo Mail account

All 11 Yahoo Mail tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Yahoo Mail → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-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.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_emails

What does the delete_emails tool do? +

Move emails to Trash folder using UIDs (soft delete, recoverable). UIDs are permanent identifiers. It is categorised as a Destructive tool in the Yahoo Mail 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 delete_emails? +

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

What risk level is delete_emails? +

delete_emails 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 delete_emails? +

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

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

delete_emails is provided by the Yahoo Mail MCP server (jtokib/yahoo-mail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yahoo Mail tool call.

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

CHECK YOUR STACK →