update_dns_records

THE RISK

Medium Risk

Why update_dns_records needs a policy

This tool modifies DNS records reversibly without deleting them (distinguishing it from delete_dns_records). DNS record updates can redirect traffic, compromise domain functionality, enable phishing, or cause service disruption, resulting in high blast radius if misused by an AI agent.

From the tool's definition Tool name 'update_dns_records' and description 'Update DNS records for a domain' indicate modification of existing DNS configuration. The Spaceship MCP Server description confirms this tool manages DNS records through the Spaceship API.

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

POLICY

How to control update_dns_records

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

policy.json

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

update_dns_records 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 Spaceship 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 Spaceship MCP Server tools

Destructive delete_dns_records Delete DNS records for a domain. Requires full record data matching the existing record. Write create_a_record Create an A record (IPv4 address) for a domain Write create_aaaa_record Create an AAAA record (IPv6 address) for a domain Write create_cname_record Create a CNAME record (canonical name/alias) for a domain Write create_dns_record Create a new DNS record for a domain Write create_mx_record Create an MX record (mail exchange) for a domain Write create_srv_record Create an SRV record (service locator) for a domain Write create_txt_record Create a TXT record (text data) for a domain

All 10 Spaceship 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 update_dns_records

What does the update_dns_records tool do? +

Update DNS records for a domain. It is categorised as a Write tool in the Spaceship 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 update_dns_records? +

Register the Spaceship MCP Server MCP server in PolicyLayer and add a rule for update_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 Spaceship MCP Server. Nothing to install.

What risk level is update_dns_records? +

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

Can I rate-limit update_dns_records? +

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

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

update_dns_records is provided by the Spaceship MCP Server MCP server (mattcollins/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Spaceship MCP Server tool call.

Start from Spaceship 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 →