New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

infra.cloudflare.dns_list

List all DNS records for a Cloudflare zone — A, AAAA, CNAME, MX, TXT, NS records with name, content, TTL, proxy status. Filter by type or name (Cloudflare)

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.cloudflare.dns-list.md

What infra.cloudflare.dns_list does on Apibase

AI agents call infra.cloudflare.dns_list to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
name string — Filter by record name (e.g. "www.example.com")
type string — Filter by record type
limit integer — Results per page (default 50, max 100)
zone_id string Yes Cloudflare Zone ID (from zones_list results)

Parameters from the server's own tool schema.

Why infra.cloudflare.dns_list is rated Low

Retrieves DNS configuration data without modification, but exposes infrastructure details valuable for reconnaissance and attacks.

From the tool's definition List all DNS records for a Cloudflare zone — A, AAAA, CNAME, MX, TXT, NS records

Questions about infra.cloudflare.dns_list

What does the infra.cloudflare.dns_list tool do? +

List all DNS records for a Cloudflare zone — A, AAAA, CNAME, MX, TXT, NS records with name, content, TTL, proxy status. Filter by type or name (Cloudflare). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does infra.cloudflare.dns_list accept? +

infra.cloudflare.dns_list accepts 4 parameters: name, type, limit, zone_id. Required: zone_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on infra.cloudflare.dns_list? +

Register the Apibase MCP server in PolicyLayer and add a rule for infra.cloudflare.dns_list: 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 Apibase. Nothing to install.

What risk level is infra.cloudflare.dns_list? +

infra.cloudflare.dns_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit infra.cloudflare.dns_list? +

Yes. Add a rate_limit block to the infra.cloudflare.dns_list 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 infra.cloudflare.dns_list completely? +

Set action: deny in the PolicyLayer policy for infra.cloudflare.dns_list. 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 infra.cloudflare.dns_list? +

infra.cloudflare.dns_list is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Apibase, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

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.