list_dns_records

THE RISK

Low Risk

Why list_dns_records needs a policy

This tool queries and retrieves DNS record data without modifying, deleting, or executing any operations. It is a read-only operation that poses minimal risk; the primary concern would be unauthorized information disclosure of DNS configuration, but the blast radius is limited to viewing existing data.

From the tool's definition Tool name is 'list_dns_records' and description states 'List all DNS records for a domain' — a retrieval operation with no side effects.

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

POLICY

How to control list_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 list_dns_records:

policy.json

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

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

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

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 list_dns_records

What does the list_dns_records tool do? +

List all DNS records for a domain. It is categorised as a Read tool in the Spaceship MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_dns_records? +

Register the Spaceship MCP Server MCP server in PolicyLayer and add a rule for list_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 list_dns_records? +

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

Can I rate-limit list_dns_records? +

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

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

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