delete_domain
Permanently delete a domain and all its mailboxes. This action is irreversible. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.
This record as markdown: /tools/trekmail-mcp-server/delete-domain.md
What delete_domain does on TrekMail MCP Server
AI agents call delete_domain to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_domain is rated Critical
This tool permanently and irreversibly deletes domains and all associated mailboxes, which cannot be undone. The blast radius is critical—loss of email infrastructure, all messages, and all user accounts within affected domains. The requirement for TREKMAIL_ALLOW_DESTRUCTIVE=true flag confirms the developers recognize this as a destructive operation. This is the most severe category applicable.
From the tool's definition Tool description explicitly states: 'Permanently delete a domain and all its mailboxes. This action is irreversible.' The tool name is 'delete_domain' and the description uses the word 'Permanently' and 'irreversible'.
Attacks that exploit this kind of access
The rule that runs delete_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_domain, this is the rule to start with:
delete_domain 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 TrekMail MCP Server, apply this rule, and every delete_domain call is checked against it from then on.
Questions about delete_domain
Permanently delete a domain and all its mailboxes. This action is irreversible. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for delete_domain: 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 TrekMail MCP Server. Nothing to install.
delete_domain 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 delete_domain 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 delete_domain. 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.
delete_domain is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
Across the catalogue