Low Risk

get_dns_records

Retrieves DNS records for a domain. If record_id is provided, retrieves a single record; otherwise, retrieves all records.

How to control get_dns_records ↓

What get_dns_records does on Porkbun MCP Server

AI agents call get_dns_records to retrieve information from Porkbun MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_dns_records needs a policy

This tool only queries and returns DNS record data without creating, modifying, deleting, or executing anything. It has no blast radius beyond potential information disclosure of DNS configuration, which is typically non-sensitive metadata. This is a straightforward Read category tool with low severity.

From the tool's definition Tool description states it 'Retrieves DNS records for a domain.' The verb 'retrieves' and the lack of any modification, deletion, or execution capability indicate this is a read-only operation. No side effects or state changes occur.

Documented attack patterns abuse exactly the kind of access get_dns_records gives an agent:

How to control get_dns_records

PolicyLayer is an MCP gateway — it sits between your AI agents and Porkbun MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dns_records:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dns_records": {}
  }
}

get_dns_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Porkbun MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_dns_records

What does the get_dns_records tool do? +

Retrieves DNS records for a domain. If record_id is provided, retrieves a single record; otherwise, retrieves all records. It is categorised as a Read tool in the Porkbun MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dns_records? +

Register the Porkbun 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 Porkbun MCP Server. Nothing to install.

What risk level is get_dns_records? +

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

Can I rate-limit get_dns_records? +

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.

How do I block get_dns_records completely? +

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.

What MCP server provides get_dns_records? +

get_dns_records is provided by the Porkbun MCP Server MCP server (miraclebakelaser/porkbun-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Porkbun MCP Server tool call.

Start from Porkbun MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

20 Porkbun MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.