delete_cloudflare_token

Delete a saved Cloudflare token and disconnect all domains using it. Domains remain in TrekMail but lose their Cloudflare connection.

Server TrekMail MCP Server trekmail/mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

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 needs a policy

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.

Questions about delete_cloudflare_token

What does the delete_cloudflare_token tool do? +

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.

How do I enforce a policy on delete_cloudflare_token? +

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.

What risk level is delete_cloudflare_token? +

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.

Can I rate-limit delete_cloudflare_token? +

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.

How do I block delete_cloudflare_token completely? +

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.

What MCP server provides delete_cloudflare_token? +

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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.