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)
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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
Attacks that exploit this kind of access
The rule that runs infra.cloudflare.dns_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra.cloudflare.dns_list, this is the rule to start with:
infra.cloudflare.dns_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.cloudflare.dns_list call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
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.
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.
infra.cloudflare.dns_list 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 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.
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.
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.
This server
Across the catalogue