Connect one or more domains to Cloudflare. Creates new TrekMail domains if they don
AI agents use connect_cloudflare_domains to create or update resources in TrekMail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.
This tool creates and modifies domain configurations by connecting them to Cloudflare and establishing new TrekMail domains. While not immediately destructive, it writes/creates infrastructure configurations that could impact email routing and domain management.
From the tool's definition The tool 'connect_cloudflare_domains' performs domain connection and creation actions: 'Connect one or more domains to Cloudflare. Creates new TrekMail domains if they don' [description cuts off].
Attacks that exploit this kind of access
Connect one or more domains to Cloudflare. Creates new TrekMail domains if they don. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for connect_cloudflare_domains: 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.
connect_cloudflare_domains is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect_cloudflare_domains 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 connect_cloudflare_domains. 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.
connect_cloudflare_domains 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.
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 →