This record as markdown: /tools/creativelead-unclick/email-delete.md
What email_delete does on UnClick
AI agents call email_delete to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
uid | string | — | |
email | string | — | |
folder | string | — | |
password | string | — |
Parameters from the server's own tool schema.
Why email_delete is rated Critical
This tool permanently removes an email message, an action that cannot be undone. Deletion is irreversible and constitutes data destruction. While the blast radius depends on which email account is targeted, the destructive nature of the operation and potential for misuse (deleting important communications, evidence, or business records) warrants a 'high' severity rating.
From the tool's definition Tool name is 'email_delete' and description states 'Delete an email by UID' — the verb 'delete' indicates irreversible removal of data.
Risk signalsAccepts file system path (folder) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs email_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_delete, this is the rule to start with:
email_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every email_delete call is checked against it from then on.
Questions about email_delete
Delete an email by UID. It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
email_delete accepts 4 parameters: uid, email, folder, password. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for email_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 UnClick. Nothing to install.
email_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the email_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.
Set action: deny in the PolicyLayer policy for email_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.
email_delete is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue