Medium Risk

edit_dns_record

Modifies an existing DNS record using its ID.

How to control edit_dns_record ↓

What edit_dns_record does on Porkbun MCP Server

AI agents use edit_dns_record to create or update resources in Porkbun MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Porkbun MCP Server environment.

Medium Risk

Why edit_dns_record needs a policy

DNS record modification is a Write action because it alters configuration reversibly. However, severity is high rather than medium because DNS changes can impact domain resolution, email delivery, and service availability if misconfigured by an agent. The tool operates on production infrastructure (Porkbun domain management) where errors have significant blast radius.

From the tool's definition Tool description states it 'Modifies an existing DNS record' — a reversible change operation. The name 'edit_dns_record' and description confirm Write category semantics (update/modify data).

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

How to control edit_dns_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 edit_dns_record:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_dns_record": {
      "limits": [
        {
          "counter": "edit_dns_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about edit_dns_record

What does the edit_dns_record tool do? +

Modifies an existing DNS record using its ID. 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 edit_dns_record? +

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

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

Can I rate-limit edit_dns_record? +

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

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

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

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.