mail_delete_message
Delete an email message by ID. This typically moves it to trash.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/mail-delete-message.md
What mail_delete_message does on AIquila — Nextcloud MCP Server
AI agents call mail_delete_message to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
messageId | number | Yes | The message ID to delete |
Parameters from the server's own tool schema.
Why mail_delete_message is rated Critical
This tool irreversibly deletes email data. While technically recoverable from trash in some systems, the primary effect is destructive removal of user data from active access. The blast radius is high: an AI agent with misuse potential could delete important messages, conversations, or evidence. This is more severe than Write (reversible modification) and qualifies as Destructive per the classification rules.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete an email message by ID.' Even though it 'typically moves it to trash,' the action irreversibly removes the message from the user's primary mailbox and cannot be trivially undone without…
Attacks that exploit this kind of access
The rule that runs mail_delete_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_delete_message, this is the rule to start with:
mail_delete_message 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 AIquila — Nextcloud MCP Server, apply this rule, and every mail_delete_message call is checked against it from then on.
Questions about mail_delete_message
Delete an email message by ID. This typically moves it to trash. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
mail_delete_message accepts 1 parameter: messageId. Required: messageId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for mail_delete_message: 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 AIquila — Nextcloud MCP Server. Nothing to install.
mail_delete_message 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 mail_delete_message 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 mail_delete_message. 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.
mail_delete_message is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
Across the catalogue