create_dnssec_record

THE RISK

Medium Risk

Why create_dnssec_record needs a policy

This tool creates new DNSSEC records, which modifies domain security settings at the registry level. While technically reversible (records can be deleted), DNSSEC misconfiguration can break domain accessibility or enable DNS spoofing attacks if exploited. The blast radius is high due to potential domain availability and security impact, making it Write rather than Read.

From the tool's definition Tool name 'create_dnssec_record' and description 'Creates a DNSSEC record at the registry for the domain' explicitly indicate irreversible creation of DNS security records that modify domain configuration.

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

POLICY

How to control create_dnssec_record

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 create_dnssec_record:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dnssec_record": {
      "limits": [
        {
          "counter": "create_dnssec_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_dnssec_record stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.

LIMIT 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 edit_dns_record Modifies an existing DNS record using its ID. Write edit_dns_record_by_name_type Edits all DNS records matching a domain, subdomain (optional), and type. Corresponds to en

All 20 Porkbun MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_dnssec_record

What does the create_dnssec_record tool do? +

Creates a DNSSEC record at the registry for the domain. It is categorised as a Write tool in the Porkbun MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dnssec_record? +

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

create_dnssec_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_dnssec_record? +

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

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

create_dnssec_record 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 →