delete_cloudflare_token
Delete a saved Cloudflare token and disconnect all domains using it. Domains remain in TrekMail but lose their Cloudflare connection.
This record as markdown: /tools/trekmail-mcp-server/delete-cloudflare-token.md
What delete_cloudflare_token does on TrekMail MCP Server
AI agents call delete_cloudflare_token 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_cloudflare_token is rated Critical
This tool performs an irreversible deletion of authentication credentials (Cloudflare token) and causes cascading disconnection of all dependent domains from their DNS management infrastructure. While the domains remain in TrekMail, the infrastructure connection is permanently severed until manually re-established, making this a destructive action with significant operational impact.
From the tool's definition Tool name contains 'delete' and description states 'Delete a saved Cloudflare token and disconnect all domains using it.' The action irreversibly removes stored credentials and severs infrastructure connections.
Attacks that exploit this kind of access
The rule that runs delete_cloudflare_token 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_cloudflare_token, this is the rule to start with:
delete_cloudflare_token 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_cloudflare_token call is checked against it from then on.
Questions about delete_cloudflare_token
Delete a saved Cloudflare token and disconnect all domains using it. Domains remain in TrekMail but lose their Cloudflare connection. 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_cloudflare_token: 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_cloudflare_token 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_cloudflare_token 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_cloudflare_token. 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_cloudflare_token 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