delete_external_account
Disconnect (remove) an external account. Nothing is deleted on the provider side. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.
This record as markdown: /tools/trekmail-mcp-server/delete-external-account.md
What delete_external_account does on TrekMail MCP Server
AI agents call delete_external_account 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_external_account is rated Critical
This tool permanently removes an external account connection from the TrekMail system. While the description clarifies that data on the provider side is not deleted, the local account linkage is irreversibly severed. The requirement for an explicit TREKMAIL_ALLOW_DESTRUCTIVE flag confirms the developers classify this as a destructive action.
From the tool's definition Tool name contains 'delete'; description states 'Disconnect (remove) an external account' and requires 'TREKMAIL_ALLOW_DESTRUCTIVE=true' environment variable, explicitly marking it as destructive.
Attacks that exploit this kind of access
The rule that runs delete_external_account 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_external_account, this is the rule to start with:
delete_external_account 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_external_account call is checked against it from then on.
Questions about delete_external_account
Disconnect (remove) an external account. Nothing is deleted on the provider side. 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_external_account: 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_external_account 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_external_account 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_external_account. 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_external_account 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