get_dnssec_records

THE RISK

Low Risk

Why get_dnssec_records needs a policy

This tool only queries and retrieves existing DNSSEC records from a domain's registry. It performs a read-only operation with no ability to modify, delete, or execute actions. The blast radius is minimal since it only exposes information about domain security records.

From the tool's definition Tool name contains 'get' and description states 'Gets the DNSSEC records' - retrieves data with no modification or side effects.

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

POLICY

How to control get_dnssec_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_dnssec_records:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dnssec_records": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Porkbun MCP Server tools

Destructive delete_dns_record Removes a specific DNS record using its ID. Destructive delete_dns_record_by_name_type Deletes all DNS records matching a domain, subdomain (optional), and type. Corresponds to Destructive delete_dnssec_record Deletes a DNSSEC record associated with the domain at the registry by Key Tag. Destructive delete_url_forward Deletes a URL forward record for a domain by its ID. Write add_url_forward Adds URL forwarding for a domain or subdomain. Write create_dns_record Adds a new DNS record to a specified domain. Write create_dnssec_record Creates a DNSSEC record at the registry for the domain. Write edit_dns_record Modifies an existing DNS record using its ID.

All 20 Porkbun MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_dnssec_records

What does the get_dnssec_records tool do? +

Gets the DNSSEC records associated with the domain at the registry. 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_dnssec_records? +

Register the Porkbun MCP Server MCP server in PolicyLayer and add a rule for get_dnssec_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_dnssec_records? +

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

Can I rate-limit get_dnssec_records? +

Yes. Add a rate_limit block to the get_dnssec_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_dnssec_records completely? +

Set action: deny in the PolicyLayer policy for get_dnssec_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_dnssec_records? +

get_dnssec_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.

CHECK YOUR STACK →