delete_inbox

Delete an inbox and all its messages.

SERVERPypi:deadsimple Email SOURCEpypi:deadsimple-email

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/deadsimple-email/delete-inbox.md

WHAT IT DOES

What delete_inbox does on Pypi:deadsimple Email

AI agents call delete_inbox to permanently remove resources in Pypi:deadsimple Email, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_inbox is rated Critical

This tool irreversibly deletes an entire inbox and all associated messages—a classic destructive action that cannot be undone. The blast radius is high because an AI agent with access could permanently lose email data, verification codes, and other critical communications.

From the tool's definition delete_inbox: Delete an inbox and all its messages

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_inbox safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:deadsimple Email, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_inbox, this is the rule to start with:

delete_inbox Hidden

delete_inbox is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pypi:deadsimple Email, apply this rule, and every delete_inbox call is checked against it from then on.

FAQ

Questions about delete_inbox

What does the delete_inbox tool do? +

Delete an inbox and all its messages. It is categorised as a Destructive tool in the Pypi:deadsimple Email 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_inbox? +

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

What risk level is delete_inbox? +

delete_inbox 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_inbox? +

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

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

delete_inbox is provided by the Pypi:deadsimple Email MCP server (pypi:deadsimple-email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pypi:deadsimple Email, and thousands of servers like it.

This server

All 14 Pypi:deadsimple Email tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →