AI agents call list_dns_records to retrieve information from Spaceship without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing DNS record data, which is a read-only operation with no side effects. Even though DNS configuration is sensitive, the tool itself only observes state without changing it. Blast radius is minimal—an AI agent misusing it can only enumerate DNS records, not modify infrastructure. Confidence is high given the explicit 'list' verb and retrieval-only nature.
From the tool's definition Tool description states 'List all DNS records for a domain' with pagination support. 'List' operations retrieve data without modification. No creation, deletion, or execution is mentioned.
Attacks that exploit this kind of access
List all DNS records for a domain. Uses pagination and can fetch all pages automatically. It is categorised as a Read tool in the Spaceship MCP Server, which means it retrieves data without modifying state.
Register the Spaceship 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. Nothing to install.
list_dns_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
list_dns_records is provided by the Spaceship MCP server (naveenkm007/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →