get_dns_records
Get all DNS records for a zone/domain
This record as markdown: /tools/0xhayd3n-cpanel-mcp-server/get-dns-records.md
What get_dns_records does on cPanel MCP Server
AI agents call get_dns_records to retrieve information from cPanel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dns_records is rated Low
This tool queries and returns existing DNS records without modifying, deleting, or executing any actions. It is a pure read operation with minimal blast radius if misused—disclosure of DNS configuration details poses low risk compared to DNS modification or deletion capabilities.
From the tool's definition Tool name 'get_dns_records' and description 'Get all DNS records for a zone/domain' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_dns_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and cPanel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dns_records, this is the rule to start with:
get_dns_records 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 cPanel MCP Server, apply this rule, and every get_dns_records call is checked against it from then on.
Questions about get_dns_records
Get all DNS records for a zone/domain. It is categorised as a Read tool in the cPanel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for get_dns_records: 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 cPanel MCP Server. Nothing to install.
get_dns_records 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 get_dns_records 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 get_dns_records. 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.
get_dns_records is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on cPanel MCP Server, and thousands of servers like it.
This server
Across the catalogue