Preview what DNS records will be created, merged, or replaced for connected Cloudflare domains. Run this before apply to see what will change.
AI agents call preview_cloudflare_dns to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only previews/shows what would happen without making any actual changes. It is a read-only operation that retrieves a diff of DNS changes, explicitly designed to be run before the actual apply step.
From the tool's definition Preview what DNS records will be created, merged, or replaced... Run this before apply to see what will change.
Attacks that exploit this kind of access
Preview what DNS records will be created, merged, or replaced for connected Cloudflare domains. Run this before apply to see what will change. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for preview_cloudflare_dns: 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.
preview_cloudflare_dns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the preview_cloudflare_dns 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 preview_cloudflare_dns. 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.
preview_cloudflare_dns 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 →